[There's a reason that Yoda is the unofficial mascot of SBS.  Size indeed matters not.] Migration Step Eleven: Figuring out what you screwed up when the install gets stuck - THE OFFICIAL BLOG OF THE SBS "DIVA"
Sun, Nov 8 2009 8:35 bradley

Migration Step Eleven: Figuring out what you screwed up when the install gets stuck

Because I checked the box in the answer file to allow me to review each screen, I got stuck with an error that it could not find the source server and to check if the source server name was wrong.

Huh?  I know that's the right name.  I checked all of my reference materials including the David Overton SBS 2008 migration book that says:

I know that name is correct, what gives?

So then I do the Shift-F10 trick.  I go to the SBS 2008 box that has a blue background and just that white box and the error screen there and there's no button to get under the operating system and to look at the log files... or is there?

Click to get your mouse on that server screen.  Hit shift-f10 at the same time and you'll get a command prompt window pop up.

Now type in explorer and hit enter.  What do you see?

A nice mouse clickable computer window that you can drill down into and find the setup log file.

C:\Program Files\Windows Small Business Server\Logs and then the setup.log file

The log file you are looking for is http://blogs.technet.com/sbs/archive/2008/10/01/key-small-business-server-2008-log-files.aspx the setup log file

And in there it says it can't ping the source server.

Huh? 

And when I go back to the command window and ping the server name, indeed, I can ping by IP, I can ping by servername.domain.lan.  I can't ping by servername only.

What the?  My IP addresses are right, I can ping in other ways, is the firewall messing me up?

And this is where signing up for that SBS 2008 newsgroup will help  https://connect.microsoft.com/sbs08/content/content.aspx?ContentID=8333  Because you need someone to bounce your "Dang, I'm stuck and I don't know what else to check" off of someone else's brain who has more brain cells than you do (especially during certain times of the install process).

Wayne Small had the necessary excess brain cells. He suggested that I check the subnet and then the netbios settings on the source server network card.

And bingo!  In the changing of the network card down to one nic from two I stupidly didn't realize that I may have flipped nics and got it on the one that had netbios disabled.  I reenabled netbios and it worked.

Once I reticked that box, the new server could ping the source server by name. 

Last but not least, I do not check the option to have the newly built server get updates DURING the install.  You are introducing change when you shouldn't be introducing patch change.

Say no.

Filed under:

# re: Migration Step Eleven: Figuring out what you screwed up when the install gets stuck

Monday, November 09, 2009 11:08 AM by Dean

Be careful with that 'get updates during install' check box. That may be refering to getting updated installation code and such not the typical security patches and windows updates. It would be good if you could confirm for us what that actually does download. Especially since you have the capability to do it in test mode.

# re: Migration Step Eleven: Figuring out what you screwed up when the install gets stuck

Monday, November 09, 2009 11:15 AM by bradley

It gets all security code updates.  There is not as of today an installer update.  If there was we'd be blogging and saying say yes.  There isn't.  They don't separate out the security from any potential installer updates.

This is why I say "no".

There's no updated installation code released.

It is only the security updates.