SBS Migration 2008 – Unable to access the source server.

Sometimes, the server cannot reach the source server due to DNS issue’s. I have worked out that you can get into the host file and add the server IP address and name.

To add it, simply control alt delete in the task manager, new task run – then head to the hosts file c:\windows\system32\drivers\etc and then hosts file. Add your entry, then try and ping it using the command prompt. You can get to this the way from run.

If you’ve done this, tried and get an authentication error, then you have a problem with connecting the source servers DNS server.

SBS Migration – Active Directory replication is taking longer than expected

I came across this error the other week while I was running a small business server 2003 to 2008.  I thought I would share with you what I did to resolve it.

While running through ‘expanding and installing files’ – the migration wizard gets stuck with the following error message.

“Active Directory replication is taking longer than expected. You can choose whether to continue waiting’

Of course, this obviously means you have AD problem from your source server. Digging a little deeper into this, I looked into the SBS install log. This is located in the programs files folder, inside of the small business server folder. – (if you want to access this, cntrl + alt + delete, task manager and then run – head to the land of explorer).

I found out the culprit.

Setup:      DsGetDcName returned: 0
Setup:      DsGetDcName returned name: sbs03.domain.local
Setup:      Expected name: sbs08.domain.local
Task:        There are 0 pending replication operations.
Setup:      Attempting LDAP bind.
Setup:      Bind successful
Task:        Waiting for replication to finish

I checked to make sure the services needed are running. I found this bit from M$. (this is on the source server)

  • Computer Browser
  • Remote Procedure Call (RPC)
  • Workstation
  • File Replication Service

after checking this, still no go. I decided to have a look further and discovered that the BurFlags registry key for FPS needed to be changed – and they’re operating incorrectly. This should normally be done by the migration wizard apparently!

Have a look at the following reg key on your source server and make sure it is decimal 4.

HK_LM\System\CurrentControlSet\Services\NTFrs\Parameters\Backup\Restore\Process at Startup - Change the BurFlags key to decimal 4

Now on the destination server, head into reg edit. (if you want to access this, cntrl + alt + delete, task manager and then run )

HK_LM\System\CurrentControlSet\Services\NTFrs\Parameters\Backup\Restore\Process at Startup – Change the BurFlags key to decimal 2
HK_LM\System\CurrentControlSet\Services\Netlogon\Parameters – change the SysVolReady - Change the key to decimal 1.

Now restart FPS on both source and destination servers. – (services.msc on the destination server from run).

Your migration should then run as normal.

 

Symantec Backup Exec 2010 – Notifcations with exchange 2007 & 2010

I  know quite a few of you have had this problem, so I thought I’d show you how to fix this. This applies for both exchange 2007 and 2010.

You need to allow exchange to accept incoming SMTP from non-authenticated applications – in our case BackupExec

Head over to your Exchange Console, into your sever configuration > hub transport > you should see receive connectors. Go and ahead and create a new connector. You want a custom connector. Call it something sensible (BackupExec and the name of the server).

I don’t like to keep stuff on standard ports, it’s just me  – so I always change this to port 26 – after this click next.

Now delete this crappy default and click the add arrow drop down to add a single IP (this the IP address of the BackupExec server – this can be the server you working on if it’s SBS)

Go ahead and finish creating this. Once done, right and click and head into the properties of the connector.

Click the permission tab and allow exchange servers.

Apply and head into the Authentication tab and click the box  ‘Externally Secured’ – nothing else in here should be ticked!!

Now ahead back over to BackupExec. Tools > Email and Pager notifications. This should all make sense now. SMTP mail server is your exchange / sbs server name. And the account your using to send the mail.

Any questions, feel free to comment.