THE OFFICIAL BLOG OF THE SBS "DIVA" : sbs 2008 migration

You wanna know the best dang resource for migrating a SBS 2003 to SBS 2008?

bradley — Sun, 23 Aug 2009 03:05:00 GMT

You wanna know the best dang resource for migrating a SBS 2003 to SBS 2008 the Microsoft way?

Small Business Server 2008 – Installation, Migration, and Configuration:
http://www.packtpub.com/small-business-server-2008-installation-migration-configuration

Buy the ebook. As it has color pictures. Why do I say that it's the best dang resource? Because it takes the Microsoft Migration documents and shows you what screens should look like along the way. I was reminded of this when I was helping someone and used it to double check a step.

But say you get stuck building a SBS 2008 box and it won't complete the install... so there you are with a SBS 2003 and a 1/2 built SBS 2008 which means there is a new server now stuck in your AD... what do you do? All is not lost, but this is where a System State backup right BEFORE you started the migration process is soooooooooo important. Because then you can restore that system state and roll back to before the migration and start over...

Step one before you do this is to reset the DSRM password so you are sure you can log in. http://support.microsoft.com/kb/322672

Then you do a DSRM 'boot' mode so that you can restore the system state -- http://support.microsoft.com/kb/240363

Once you do that, go back to Philip's checklist as a guide -- http://blog.mpecsinc.ca/2009/06/sbs-2003-to-sbs-2008-migration-guide.html and redo step number 10 so that you are sure the AD is clean again

Run the IT health scanner tool - https://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=dd7a00df-1a5b-4fb6-a8a6-657a7968bd11

And don't forget to review all the "gotchas" that might nail you from here -- http://blogs.technet.com/sbs/archive/2009/02/19/sbs-2008-migrations-from-sbs-2003-keys-to-success.aspx

The following are run from the command prompt to test Active Directory health:
DCDiag

- DCDiag [Enter]
- DCDiag /test:DNS
- DCDiag /? (List of switches)

NetDiag
RepAdmin

- RepAdmin /viewlist *
- RepAdmin /SyncAll
- RepAdmin /KCC

NetDom /query FSMO

And also rerun the http://www.ebspreptool.com/ to ensure your AD is clean and then rerun the source tool prep and start all over again.

Migrate sbs 2000 to sbs 2008

bradley — Wed, 15 Jul 2009 02:21:00 GMT

GetAFreelancer.com - Migrate sbs 2000 to sbs 2008 | Windows:
http://www.getafreelancer.com/projects/geekinterview_452149.html

Description

Looking for an experienced windows admin - this job requires great english, and remote access virtuosity! Prefer US candidates but will consider great international ones. You need to comfortable both doing your work via remote access and walking users through problems.

to be considered, I need you to give me an estimate of how many hours you estimate the job will take, and evidence of experience with this work (resume, tests completed, feedback received etc)

We would want the person/company who installs the server to also be available for ongoing support - so I will give preference to those who can do that.

Expertise in:
SBS 2000 & 2008
Dell remote access card (installed in new server)
Logmein, vnc, etc
Migration - must have done this before
Blackberry enterprise server

.....

-Install blackberry enterprise server on new server & help connect devices to it

-------------

One problem that I see with this RFP is that you can't install the Blackberry enterprise server on the SBS 2008 box. So far of all of the migration gotchas I've seen that's the one that concerns me the most because it's the one that all of us, including me think "well of course it allows it to be installed on a SBS box because it supports Win2k8 right?" That's the once scenerio that has me the most concerned that customers and partners won't be aware of.

So when the instructions say do this... you want to do that.

bradley — Tue, 07 Jul 2009 07:06:00 GMT

Download details: SBS 2008 Migration Checklist:
http://www.microsoft.com/downloads/details.aspx?FamilyID=f67148da-cba8-4222-8ae5-136a6597a340&displayLang=en
Download details: Windows SBS 2003 to 2008 Migration Guide:
http://www.microsoft.com/downloads/details.aspx?FamilyID=52b7ea63-78af-4a96-811e-284f5c1de13b&displaylang=en

When you read those migration instruction, you need to follow e-v-e-r-y step. Every single step is important and needs to be done. Every single step needs to be performed. Every single one.

Don't second guess the instructions here, they were tested and done until everyone is blue in the face.

So when the instructions say do this... you want to do that.

The Official SBS Blog : SBS Migrations: Troubleshooting Moving Public Folder Replicas

bradley — Mon, 22 Jun 2009 06:13:00 GMT

The Official SBS Blog : SBS Migrations: Troubleshooting Moving Public Folder Replicas:
http://blogs.technet.com/sbs/archive/2009/06/21/sbs-migrations-troubleshooting-moving-public-folder-replicas.aspx

Must have links you need to have to do a SBS 2008 migration:

bradley — Sat, 20 Jun 2009 19:40:00 GMT

Must have links and resources you need to have to do a SBS 2008 migration:

www.sbsmigrationtips.com (aka the SBS blog post keys to success)

MPECS Inc. Blog: SBS 2003 to SBS 2008 Migration Guide – v1.0.1:
http://blog.mpecsinc.ca/2009/06/sbs-2003-to-sbs-2008-migration-guide.html

Active Directory Clean-up prep for SBS migration | Third Tier:
http://www.thirdtier.net/2009/06/active-directory-clean-up-prep-for-sbs-migration/

Windows Small Business Server 2008 Migration : John R. Pattison:
http://www.johnrpattison.com/blog/windows-small-business-server-2008/windows-small-business-server-2008-migration/

And if you are looking for a book on the process, David Overton has probably the best guide I've found because it explains the migration as well as gives screen shots. If you want to order a book you can, but the pdf feature is very nice.

Small Business Server 2008 – Installation, Migration, and Configuration:
http://www.packtpub.com/small-business-server-2008-installation-migration-configuration/book

Tattoo this on your forehead

bradley — Fri, 19 Jun 2009 00:24:00 GMT

Today the SBS blog updated their "Success in SBS 2003 to 2008 Migration" blog post.

You know the blog post I say you should have tattooed to your forehead. Well since http://blogs.technet.com/sbs/archive/2009/02/19/sbs-2008-migrations-from-sbs-2003-keys-to-success.aspx is a bit long to be tattooing to anyone's forehead, so I'll make it easy for you. You now only have to tattoo this on your forehead http://www.sbsmigrationtips.com/

Better than the teen with the too many stars on her face I suppose.

So now you have it...... http://www.sbsmigrationtips.com/

And today it's been updated for some NEW best tips...

O. Disable WSUS on Source domain prior to migration

If you have a deadline set for a Windows 2008 update in WSUS that is past-due, your SBS 2008 setup can fail when the update is automatically installed and the SBS 2008 server is rebooted. Deadlines are not automatically set in SBS 2003 but can be set by the Admin through the native WSUS console. We recommend disabling WSUS for the duration of the migration.

P. On the Source Server run the Exchange 2007 Readiness Check in the Exchange BPA

Q. Make sure the Admin account you are using for the migration has a STRONG password

Strong passwords must meet the following minimum requirements:

Passwords cannot contain the user's account name or parts of the user's full name that exceed two consecutive characters.
Passwords must be at least six characters in length.
Passwords must contain characters from three of the following four categories:
- English uppercase characters (A through Z).
- English lowercase characters (a through z).
- Base 10 digits (0 through 9).
- Non-alphabetic characters (for example, !, $, #, %).

(I finally parked a godaddy redirect as basically I'm lazy and got tired of trying to google that blog post all the time)

SBS Best Practice

bradley — Sat, 09 May 2009 21:22:00 GMT

Listening to the SBS build day presented by Tim Carney in Las Vegas and the statement was made to run the SBSbestpractice Analyzer (found at www.sbsbpa.com and run it on your SBS 2003 before you migrate.

Also read this post - http://blogs.technet.com/sbs/archive/2009/02/19/sbs-2008-migrations-from-sbs-2003-keys-to-success.aspx

and run the EBS tool on the box as that will ensure that your AD is healthy BEFORE you begin the migration.

Migrating from SBS 2000 to SBS 2008

bradley — Sun, 03 May 2009 00:49:00 GMT

This document written by Microsoft Support Engineer Edwin Joseph describes the process that you should follow to successfully migrate settings and data from an existing server running Microsoft Small Business Server 2000 to a new computer running Windows SBS 2008.

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=b86e2af5-782b-4001-bf86-d872028a4619

http://blogs.technet.com/11/archive/2009/05/02/finally-it-is-here-migrating-microsoft-small-business-server-2000-to-windows-small-business-server-2008.aspx

"We're moving a lot more stuff ...."

bradley — Sun, 05 Apr 2009 03:40:00 GMT

http://www.greatlittlebook.com/Seminars/ConCalls/SMB_Conference_Call_20090401.mp3

"We're moving a lot more stuff ...."

The sound may be bad, but the listen is still worth it. (and no apologies needed Karl, it's worth the pops and blips and clicks)

SMB Conference Call #35:
Jeff Middleton -- Download Now

SBS Migrations from Jeff Middleton and SBSMigration.com

NOTE: This is a poor quality recording. It is not being broadcast to iTunes or the RSS feed. In addition to being recorded in an airport, it is cut off short (37 minutes in). Our apologies for this. I know die-hard fans will listen to anything, so I'm putting it up. But you've been warned!

About Jeff:

Event Organizer: www.conference.sbsmigration.com
SBS Migration Specialist: www.sbsmigration.com
Jeff's Email: jeff@sbsmigration.com

Making sure you have a clean AD

bradley — Thu, 26 Mar 2009 04:56:00 GMT

One of the best ways to ensure you have happy migrations is to ensure you have happy Active Directories.

Download details: Windows Server 2003 Service Pack 2 32-bit Support Tools:
http://www.microsoft.com/downloads/details.aspx?FamilyID=96a35011-fd83-419d-939b-9a772ea2df90&DisplayLang=en#filelist
One of the tools to download and run on the SBS 2003 before you start the migration is dcdiag which is included in that download.

Move yourself to the support subdirectory and run the tool and make sure you have a happy camper

C:\WINDOWS\system32>cd\program files

C:\Program Files>cd support tools

C:\Program Files\Support Tools>dcdiag

Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\DOMAIN
      Starting test: Connectivity
         ......................... DOMAIN passed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\DOMAIN
      Starting test: Replications
         ......................... DOMAIN passed test Replications
      Starting test: NCSecDesc
         ......................... DOMAIN passed test NCSecDesc
      Starting test: NetLogons
         ......................... DOMAIN passed test NetLogons
      Starting test: Advertising
         ......................... DOMAIN passed test Advertising
      Starting test: KnowsOfRoleHolders
         ......................... DOMAIN passed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... DOMAIN passed test RidManager
      Starting test: MachineAccount
         ......................... DOMAIN passed test MachineAccount
      Starting test: Services
            IsmServ Service is stopped on [DOMAIN]
         ......................... DOMAIN failed test Services
      Starting test: ObjectsReplicated
         ......................... DOMAIN passed test ObjectsReplicated
      Starting test: frssysvol
         ......................... DOMAIN passed test frssysvol
      Starting test: frsevent
         ......................... DOMAIN passed test frsevent
      Starting test: kccevent
         ......................... DOMAIN passed test kccevent
      Starting test: systemlog
         ......................... DOMAIN passed test systemlog
      Starting test: VerifyReferences
         ......................... DOMAIN passed test VerifyReferences

   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom

   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom

   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom

   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom

   Running partition tests on : DOMAINNAME
      Starting test: CrossRefValidation
         ......................... DOMAINNAME passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... DOMAINNAME passed test CheckSDRefDom

   Running enterprise tests on : DOMAINNAME.lan
      Starting test: Intersite
         ......................... DOMAINNAME.lan passed test Intersite
      Starting test: FsmoCheck
         ......................... DOMAINNAME.lan passed test FsmoCheck

C:\Program Files\Support Tools>

Mind you some things like that IsmServ (what the heck is that?) can be ignored (thank you Philip - http://blog.mpecsinc.ca/2008/07/sbs-dcdiag-produces-ismserv-error.html )

Then take a look at the Directory Service, the DNS Server and the File Replication Server logs.

Make sure they are happy event logs. No journal wrap, no red warnings. Nice and happy blue information marks.

Mind you, you can have some old DNS event log errors, but they can be as a result of rebooting the box (and SBS tripping over it's toes) and if you see that it's now happy as a clam again, you can give the server a clean bill of health before starting the process.

Bottom line check out your AD first before you start the migration process.

SBSC Canada Blog : Technical Labcasts for SBS/EBS 2008 available on-demand!:

bradley — Fri, 13 Mar 2009 04:10:00 GMT

SBSC Canada Blog : Technical Labcasts for SBS/EBS 2008 available on-demand!:
http://blogs.msdn.com/cdnsbsc/archive/2009/03/12/technical-labcasts-for-sbs-ebs-2008-available-on-demand.aspx

Okay so want to walk through a migration without standing up a test box? Look at the content on those labcasts. Mind you I didn't go all the way through it but just fired it up enough to see what it was all about but the link on the migration lab looks promising.

Migrating from SBS 2003 to SBS 2008: Lab

Check it out!

Windows SBS Active Directory Group Converter

bradley — Thu, 05 Mar 2009 04:08:00 GMT

Windows SBS Active Directory Group Converter:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=7fa26c89-7106-41a3-a7b1-dad38beeacf8

The Windows Small Business Server 2008 Active Directory Group Converter helps you convert groups in the MyBusiness organizational unit to groups that are compatible with Windows SBS 2008.

You can convert groups that were created by using either the Windows SBS 2003 Administration Console or the Active Directory Users and Groups console. To convert the groups, the wizard adds some necessary Active Directory attributes to them.

After you convert groups to Windows SBS 2008 compatible groups, you can manage the groups by using the Windows SBS Console.

Obviously when your only groups are leftover from a SQL install this doesn't make much sense, but for those looking for an easier way to convert groups in the migration, this is the tool for you.

Old 8.3 file names are still kicking in the 2008 era

bradley — Thu, 26 Feb 2009 08:16:00 GMT

A note from Tony:

Some information for your after using yor blogs for years for help and assistnace...

If you happen to have old DOS / Netware applications that use data off  a network share... yes they are still out there.... and work in vista....

By defualt SBS 2008 has 8dot3 filenames turned off and these old applications will not work..

run cmd as Administrator

fsutil behavior query disable8dot3   ( result of 1 is on  o is off )

fsutil behsvior set disable8dot3 0

REboot required.... but to reset the filenames the data has to be copied off the server, deleted and copied back...file by file...

robocopy to the rescue again...

Thanks for your Help
Regards
Tony

A little migration tip from Shane

bradley — Thu, 26 Feb 2009 08:13:00 GMT

Shout out tonight (this morning) to Shane Scanlon from Comcity Technology in Melbourne Australia. He apparently tortures his staff by making them read my blog.

He passed this along:

Thought Id share this one with you as its a nice tip for the young players: 

If you shutdown the SBS2003 before the demote and remove exchange part. Then restart the SBS2008 server the Exchange Store 
will not mount and the following errors are seen in the Event Logs: (Note name has been changed of the server:domain below
for security reasons)

Note once you demote and remove exchange on the SBS2003 server as per migration guide these errors no longer occur. 

Log Name:      Application
Source:        MSExchange ADAccess
Date:          24/02/2009 7:44:42 PM
Event ID:      2114
Task Category: Topology
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      OCS.Our.local
Description:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=2556). Topology discovery failed, error 0x80040952 (LDAP_LOCAL_ERROR (Client-side internal error or bad LDAP message)). 
Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." 
Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchange ADAccess" />
    <EventID Qualifiers="49156">2114</EventID>
    <Level>2</Level>
    <Task>3</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-02-24T08:44:42.000Z" />
    <EventRecordID>16873</EventRecordID>
    <Channel>Application</Channel>
    <Computer>OCS.Our.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>MSEXCHANGEADTOPOLOGYSERVICE.EXE</Data>
    <Data>2556</Data>
    <Data>80040952</Data>
    <Data>LDAP_LOCAL_ERROR (Client-side internal error or bad LDAP message)</Data>
  </EventData>
</Event>

Log Name:      Application
Source:        MSExchange ADAccess
Date:          24/02/2009 7:45:29 PM
Event ID:      2501
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      OCS.Our.local
Description:
Process MSEXCHANGEADTOPOLOGY (PID=2556). The site monitor API was unable to verify the site name for this Exchange computer - Call=HrSearch Error code=80040a01. 
Make sure that Exchange server is correctly registered on the DNS server.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchange ADAccess" />
    <EventID Qualifiers="49156">2501</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-02-24T08:45:29.000Z" />
    <EventRecordID>16998</EventRecordID>
    <Channel>Application</Channel>
    <Computer>OCS.Our.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>MSEXCHANGEADTOPOLOGY</Data>
    <Data>2556</Data>
    <Data>HrSearch</Data>
    <Data>80040a01</Data>
  </EventData>
</Event>

Log Name:      Application
Source:        MSExchange ADAccess
Date:          24/02/2009 7:45:29 PM
Event ID:      2601
Task Category: General
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      OCS.Our.local
Description:
Process MSEXCHANGEADTOPOLOGY (PID=2556). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, 
Exchange could not retrieve the SID for account <WKGUID=DC1301662F547445B9C490A52961F8FC,CN=Microsoft Exchange,CN=Services,CN=Configuration,...> - Error code=80040a01. 
 The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchange ADAccess" />
    <EventID Qualifiers="32772">2601</EventID>
    <Level>3</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-02-24T08:45:29.000Z" />
    <EventRecordID>16999</EventRecordID>
    <Channel>Application</Channel>
    <Computer>OCS.Our.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>MSEXCHANGEADTOPOLOGY</Data>
    <Data>2556</Data>
    <Data>&lt;WKGUID=DC1301662F547445B9C490A52961F8FC,CN=Microsoft Exchange,CN=Services,CN=Configuration,...&gt;</Data>
    <Data>80040a01</Data>
  </EventData>
</Event>

Log Name:      Application
Source:        MSExchangeIMAP4
Date:          24/02/2009 7:46:33 PM
Event ID:      2011
Task Category: (1)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      OCS.Our.local
Description:
ServicePrincipalName.RegisterServiceClass returned error code -2146892976. The process will exit.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchangeIMAP4" />
    <EventID Qualifiers="49156">2011</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-02-24T08:46:33.000Z" />
    <EventRecordID>17013</EventRecordID>
    <Channel>Application</Channel>
    <Computer>OCS.Our.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>-2146892976</Data>
  </EventData>
</Event>


Shane Scanlon
Comcity Technology 
Melbourne Australia

Don't untick the IPv6 box

bradley — Sun, 08 Feb 2009 18:40:00 GMT

http://windowsitpro.com/article/articleid/100210/troubleshooting-a-slow-running-windows-server-2008.html

"We've had numerous hang ups with file shares on Windows Server 2008 using MR2. Also disabling IPv6 seems to help. We've noticed a significant performance (+80%) increase in backups with Backup Exec by upgrading to MR3 and disabling IPv6 support."

And that is the worst possible thing you can do to a SBS 2008 server.

http://blogs.technet.com/sbs/archive/2008/10/24/issues-after-disabling-ipv6-on-your-nic-on-sbs-2008.aspx

If you want a box that will take 45 minutes to reboot, untick the box.

If you want all network connectivity to freak out, untick the box.

If you want Exchange to fail to bind to AD, untick the box.

Bottom line on SBS 2008, DON'T untick the box and ensure that it's there. If you get called in on an ailing system, check FIRST to ensure that IPv6 is checked in the network card.

That Internet Protocol Version 6 NEEDS to be checked.

Watch that CA name

bradley — Sun, 01 Feb 2009 07:36:00 GMT

When you do a SBS 2003 to SBS 2008 migration, one of the gotchas that can nail you in the rear is a gotcha that if you misread the answer file, and put something in there that you shouldn't ends up causing you to have to use a Remote Web Workplace URL other than the expected remote.domain.com

SeanDaniel.com - Small Business Server and Other Technology: Gotcha's Using the SBS 2008 Answer File:
http://sbs.seandaniel.com/2008/08/gotcha-using-sbs-2008-answer-file.html

When you use the answerfile in the SBS migration, make sure that you leave the box for the Certificate Authority name totally BLANK. Do not put in remote.domain.com. If you do when you run the Set up your Internet Address wizard it will fail. Consistently on remote.domain.com. When you look at the log files in the DPCW.log file it may not be obvious what the problem is. It's only obvious when you compare it to a clean box that works:

This is what you see in a log file that uses remote.domain.com as the Certificate Authority name in the answer file (remember this is the WRONG thing to do)

[3256] 090123.145451.1200: CoreNet: Getting root cert
[3256] 090123.145451.1512: CoreNet: CA ConfigString: SBS2008.domain.local\remote.domain.com
[3256] 090123.145451.1668: CoreNet: CA ConfigString: SBS2008.domain.local\remote.domain.com

This is what it looks like on one that works:

[6968] 090131.220320.5839: CoreNet: Getting root cert
[6968] 090131.220320.6464: CoreNet: CA ConfigString: SERVER.smallbizco.local\smallbizco-SERVER-CA
[6968] 090131.220320.6777: CoreNet: CA ConfigString: SERVER.smallbizco.local\smallbizco-SERVER-CA

See the difference? That CA is server.domain.local\CA proper name. It cannot be remote.domain.com otherwise the Domain name wizard will not work.

One solution to the problem is to go into the Advanced settings and use some other URL:

Once in there then remove "remote" and use something else instead to prepend the web site URL for Remote Web Workplace access. Because the CA is remote.domain.com as set by the answer file, you can't now use remote.domain.com as your Domain name.

Icky lesson to learn but next time, leave the CA box blank.

Thank you Peter for sharing your experience (and log files) on this!

SBS 2003 to SBS 2008 migration thoughts and issues

bradley — Wed, 21 Jan 2009 01:18:00 GMT

So those of you that have gone through a SBS 2008 migration, David has some questions to ask of you. And this is where that feedback loop comes into play. While if you are not UK based, you don't have to flood David's mailbox, you can still post in the various community venues or even in the comments on this blog some of the key things you've experienced and you feel should be looked at/addressed/discussed.

I see the health of AD to be a big sticking point for some folks as well. What have you seen?

SBS 2003 to SBS 2008 migration thoughts and issues - David Overton's Blog - David Overton's Blog and Discussion Site:
http://davidoverton.com/blogs/doverton/archive/2009/01/19/sbs-2003-to-sbs-2008-migration-thoughts-and-issues.aspx

I've been part of a lively debate on the Yahoo UK SBS Group about how to migrate from SBS 2003 to SBS 2008 and what the issues are. The information I have so far is good, but I need much more to take it to the product teams.

For sure, the issues so far are:

   * Concerns around the "state" of AD before a migration is started -
     how do you check it - look at this blog post
     <http://davidoverton.com/blogs/doverton/archive/2009/01/19/active-directory-health-check-make-sure-your-ad-is-healthy-before-you-migrate-sbs-2003-to-sbs-2008.aspx>

   * Concerns around the Exchange migration in terms of time taken and
     failure scenarios - how to remove the chances of this?
   * Concerns around "on-site" versus "off-site" strategies
   * Concerns around recovery options in the event of failures (restore
     from backup not being ideal if you want it diagnosed)

My problem is that I have no data to take to the Microsoft product teams, which means I can't ask them to fix things so this is a two fold open invitation.

1. If you have had an issue, share it via comments below, but also
     PLEASE e-mail (doverton@microsoft.com
     <mailto:doverton@microsoft.com?subject=migration%20issues>) as
     well so I can get in touch with you and potentially the product
     teams too. If you put your mail in the blog then others can see
     it. You are also welcome to just e-mail me, but then there will
     not be discussion in public, which might be a shame.
2. Share other concerns so I can get them documented and addressed,
     but also use the Microsoft support - you can always send me the SR
     numbers if you want me to tie them together.

That is it - may the knowledge sharing continue!

Make that complex please!

bradley — Fri, 09 Jan 2009 07:40:00 GMT

So when you do a SBS 2008 migration and don't put in a complex enough password during the migration install it may not be intially obvious that it didn't like the password.

But just keep that in mind. Make sure that the password you choose for the new server is complex.

Capital letters

Numbers

Spaces

Funky characters

Just make in complex!

http://blogs.technet.com/sbs/archive/2009/01/02/introducing-the-windows-sbs-2008-answer-file.aspx

Administrator Password: Password for the new network administrator account. The password that you provide must be complex. If you do not provide a complex password, the unattended installation stops so you can provide the complex password.

Migration Concepts with SBS 2008

bradley — Fri, 09 Jan 2009 05:26:00 GMT

Part two of the announcements tonight is tomorrow's 50/50 webcast on Migration

(yes it will be recorded)

Migration Concepts with SBS 2008
Presented by Jeff Middleton

Microsoft Partners 5W/50 Series
January 9, 2009
9:00 AM - 10:00 AM

Time Zone (GMT-08:00) Pacific Time (US & Canada)

Register for the Webcast:
https://training.partner.microsoft.com/plc/details.aspx?publisher=12&delivery=259602

Migration projects pose unique challenges for IT Consultants. The goal is to move a customer's server infrastructure into a new product and platform with a process that is both predictable and profitable.
Jeff Middleton will present the concepts of the Microsoft documented "join to domain" approach as well as the options with an updated for SBS 2008 Swing Migration technique. In addition to a technical review of the project path elements, join us for Jeff's insights into the planning strategy concerns on these additional points to be discussed:

* The Transition Timeline & Value Budget
* Establishing Roll-Back, Pause or Completion Goals
* What's implied in Multi-Server Deployments?
* Where is the Automation?
* Including your Value-Add of Quality & Predictability

Health of the server

bradley — Tue, 06 Jan 2009 07:07:00 GMT

One of the recommendations that the migration docs say is to run some DNS tools to check the health of the server.

Run the Windows Support Tools
If your server is running Windows Server 2003 Standard Edition, you cannot use the Best Practices Analyzer, but you can use the Windows Support Tools to accomplish the same task. The following table lists the tools that you can use to diagnose issues on your server, network, and domain:

Tool Description

Netdiag.exe
Helps isolate networking and connectivity issues.

Dcdiag.exe
Analyzes the state of domain controllers in a forest or enterprise, and reports issues to assist you in troubleshooting.

Repadmin.exe
Assists you in diagnosing replication issues between domain controllers.

The tools are included in here:
Download details: Windows Server 2003 Service Pack 1 32-bit Support Tools:
http://www.microsoft.com/downloads/details.aspx?familyid=6EC50B78-8BE1-4E81-B3BE-4E7AC4F0912D&displaylang=en

(this is on a vmware of a SBS 2003 test domain)

C:\Program Files\Support Tools>dir
Volume in drive C has no label.
Volume Serial Number is 8CB7-39FD

Directory of C:\Program Files\Support Tools

01/05/2009 11:21 PM    <DIR>          .
01/05/2009 11:21 PM    <DIR>          ..
03/24/2005 07:46 PM            91,648 acldiag.exe
03/24/2005 07:46 PM           216,091 addiag.exe
03/24/2005 07:46 PM           349,696 adsiedit.dll
03/24/2005 07:46 PM            42,986 adsiedit.msc
03/24/2005 07:46 PM             8,704 apmstat.exe
03/24/2005 07:46 PM            18,432 bindiff.exe
03/24/2005 07:46 PM           119,808 Bitsadmin.exe
03/24/2005 07:46 PM            41,472 browstat.exe
03/24/2005 07:46 PM            65,024 cabarc.exe
03/24/2005 07:46 PM            81,676 clone.vbs
03/24/2005 07:46 PM            33,262 clonegg.vbs
03/24/2005 07:46 PM            33,418 cloneggu.vbs
03/24/2005 07:46 PM            33,315 clonelg.vbs
03/24/2005 07:46 PM            91,648 clonepr.dll
03/24/2005 07:46 PM            97,280 clonepr.doc
03/24/2005 07:46 PM            32,855 clonepr.vbs
03/24/2005 07:46 PM             8,293 connstat.cmd
03/24/2005 07:46 PM           459,264 dcdiag.exe
03/24/2005 07:46 PM             1,317 depends.cnt
03/24/2005 07:46 PM             8,704 depends.dll
03/24/2005 07:46 PM           642,048 depends.exe
03/24/2005 07:46 PM           128,430 depends.hlp
03/24/2005 07:46 PM            55,808 devcon.exe
03/24/2005 07:46 PM           235,008 dfsutil.exe
03/24/2005 07:46 PM            13,824 dhcploc.exe
03/24/2005 07:46 PM            15,360 diruse.exe
03/24/2005 07:46 PM           160,768 dmdiag.exe
03/24/2005 07:46 PM           132,096 dnscmd.exe
03/24/2005 07:46 PM            82,432 dnslint.exe
03/24/2005 07:46 PM            45,568 dsacls.exe
03/24/2005 07:46 PM           125,440 dsastat.exe
03/24/2005 07:46 PM            25,408 dskprobe.chm
03/24/2005 07:46 PM           131,072 dskprobe.exe
03/24/2005 07:46 PM            15,872 efsinfo.exe
03/24/2005 07:46 PM            26,112 exctrlst.exe
03/24/2005 07:46 PM            14,336 filever.exe
03/24/2005 07:46 PM            26,112 ftonline.exe
03/24/2005 07:46 PM             5,632 getsid.exe
03/24/2005 07:46 PM            34,304 gflags.exe
03/24/2005 07:46 PM             8,333 health_chk.cmd
03/24/2005 07:46 PM            16,384 httpcfg.exe
03/24/2005 07:46 PM           843,827 iadstools.dll
03/24/2005 07:46 PM           170,496 iadstools.doc
03/24/2005 07:46 PM            39,424 iasparse.doc
03/24/2005 07:46 PM            37,376 iasparse.exe
03/24/2005 07:46 PM            20,992 inetorgpersonfix.doc
03/24/2005 07:46 PM             1,000 inetorgpersonfix.ldf
03/24/2005 07:46 PM            10,556 iologsum.cmd
03/24/2005 07:46 PM            23,040 ksetup.exe
03/24/2005 07:46 PM            90,112 ktpass.exe
03/24/2005 07:46 PM        14,031,229 ldp.doc
03/24/2005 07:46 PM           263,168 ldp.exe
03/24/2005 07:46 PM             7,680 lowiosrv.dll
03/24/2005 07:46 PM             2,996 lowiosrv.tlb
03/24/2005 07:46 PM            19,456 memsnap.exe
03/24/2005 07:46 PM            27,648 movetree.dll
03/24/2005 07:46 PM            10,240 movetree.exe
03/24/2005 07:46 PM            17,408 msicuu.exe
03/24/2005 07:46 PM            89,088 msizap.exe
03/24/2005 07:46 PM            48,640 netcap.exe
03/24/2005 07:46 PM           390,144 netdiag.exe
03/24/2005 07:46 PM           183,808 netdom.exe
03/24/2005 07:46 PM           196,096 nltest.exe
03/24/2005 07:46 PM            10,240 ntfrsutl.exe
03/24/2005 07:46 PM            26,112 poolmon.exe
03/24/2005 07:46 PM            23,040 portqry.exe
03/24/2005 07:46 PM            16,393 readme.htm
03/24/2005 07:46 PM            37,376 remote.exe
03/24/2005 07:46 PM           244,736 repadmin.exe
03/24/2005 07:46 PM         1,191,987 replmon.exe
03/24/2005 07:46 PM            14,848 rsdiag.exe
03/24/2005 07:46 PM            15,872 rsdir.exe
03/24/2005 07:46 PM         1,233,920 rstools.dll
03/24/2005 07:46 PM            26,112 sdcheck.exe
03/24/2005 07:46 PM            19,909 search.vbs
03/24/2005 07:46 PM            13,312 setspn.exe
03/24/2005 07:46 PM            60,416 showaccs.exe
03/24/2005 07:46 PM             4,404 sidhist.vbs
03/24/2005 07:46 PM            55,296 sidwalk.exe
03/24/2005 07:46 PM             4,608 sidwalk.msc
03/24/2005 07:46 PM           105,984 sidwkr.dll
03/24/2005 07:46 PM            19,968 spcheck.exe
03/24/2005 07:46 PM             4,239 spcheck.ini
03/24/2005 07:46 PM            16,054 topchk.cmd
03/24/2005 07:46 PM           140,288 windiff.exe
03/24/2005 07:46 PM            17,357 windiff.hlp
03/24/2005 07:46 PM            63,488 xcacls.exe
              87 File(s)     23,665,623 bytes
               2 Dir(s) 31,048,130,560 bytes free

C:\Program Files\Support Tools>netdiag

........................................

    Computer Name: SERVER
    DNS Host Name: SERVER.smallbusiness.local
    System info : Microsoft Windows Server 2003 (Build 3790)
    Processor : x86 Family 6 Model 23 Stepping 6, GenuineIntel
    List of installed hotfixes :
        KB924667-v2
        KB925398_WMP64
        KB925902-v2
        KB927891
        KB929123
        KB930178
        KB932168
        KB933729
        KB933854
        KB935839
        KB935840
        KB936357
        KB936782
        KB938127
        KB938127-IE7
        KB938464
        KB941569
        KB942830
        KB942831
        KB943055
        KB943460
        KB943485
        KB943729
        KB944338-v2
        KB944653
        KB945553
        KB946026
        KB948496
        KB948745
        KB949014
        KB950762
        KB950974
        KB951066
        KB951698
        KB951746
        KB951748
        KB952069
        KB952954
        KB953838-IE7
        KB954211
        KB954600
        KB955069
        KB955839
        KB956390-IE7
        KB956391
        KB956802
        KB956803
        KB956841
        KB957095
        KB957097
        KB958215
        KB958215-IE7
        KB958644
        KB960714
        KB960714-IE7
        Q147222

Netcard queries test . . . . . . . : Passed

Per interface results:

Adapter : Server Local Area Connection

Netcard queries test . . . : Passed

        Host Name. . . . . . . . . : SERVER
        IP Address . . . . . . . . : 192.168.220.140
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . :
        Primary WINS Server. . . . : 192.168.220.140
        Dns Servers. . . . . . . . : 192.168.220.140

AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Skipped
[WARNING] No gateways defined for this adapter.

        NetBT name test. . . . . . : Passed
        [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenge
r Service', <20> 'WINS' names is missing.
            No remote names have been found.

WINS service test. . . . . : Passed

Adapter : Network Connection

Netcard queries test . . . : Passed

        Host Name. . . . . . . . . : SERVER.Kikibitzrtm.local
        IP Address . . . . . . . . : 192.168.16.22
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . : 192.168.16.2
        Primary WINS Server. . . . : 192.168.220.140
        NetBIOS over Tcpip . . . . : Disabled
        Dns Servers. . . . . . . . : 192.168.220.140

AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Skipped
NetBT is disabled on this interface. [Test skipped]

WINS service test. . . . . : Skipped
NetBT is disable on this interface. [Test skipped].

Global results:

Domain membership test . . . . . . : Passed

NetBT transports test. . . . . . . : Passed
    List of NetBt transports currently configured:
        NetBT_Tcpip_{EBD674F4-D3A6-4B64-8ACC-5195EA6DA5DB}
    1 NetBt transport currently configured.

Autonet address test . . . . . . . : Passed

IP loopback ping test. . . . . . . : Passed

Default gateway test . . . . . . . : Passed

NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.

Winsock test . . . . . . . . . . . : Passed

DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server '192.168.220.
140'.

Redir and Browser test . . . . . . : Passed
    List of NetBt transports currently bound to the Redir
        NetBT_Tcpip_{EBD674F4-D3A6-4B64-8ACC-5195EA6DA5DB}
    The redir is bound to 1 NetBt transport.

    List of NetBt transports currently bound to the browser
        NetBT_Tcpip_{EBD674F4-D3A6-4B64-8ACC-5195EA6DA5DB}
    The browser is bound to 1 NetBt transport.

DC discovery test. . . . . . . . . : Passed

DC list test . . . . . . . . . . . : Passed

Trust relationship test. . . . . . : Skipped

Kerberos test. . . . . . . . . . . : Passed

LDAP test. . . . . . . . . . . . . : Passed

Bindings test. . . . . . . . . . . : Passed

WAN configuration test . . . . . . : Skipped
No active remote access connections.

Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

Note: run "netsh ipsec dynamic show /?" for more detailed information

The command completed successfully

C:\Program Files\Support Tools>

C:\Program Files\Support Tools>dcdiag

Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\SERVER
      Starting test: Connectivity
         ......................... SERVER passed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\SERVER
      Starting test: Replications
         ......................... SERVER passed test Replications
      Starting test: NCSecDesc
         ......................... SERVER passed test NCSecDesc
      Starting test: NetLogons
         ......................... SERVER passed test NetLogons
      Starting test: Advertising
         ......................... SERVER passed test Advertising
      Starting test: KnowsOfRoleHolders
         ......................... SERVER passed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... SERVER passed test RidManager
      Starting test: MachineAccount
         ......................... SERVER passed test MachineAccount
      Starting test: Services
            IsmServ Service is stopped on [SERVER]
         ......................... SERVER failed test Services
      Starting test: ObjectsReplicated
         ......................... SERVER passed test ObjectsReplicated
      Starting test: frssysvol
         ......................... SERVER passed test frssysvol
      Starting test: frsevent
         ......................... SERVER passed test frsevent
      Starting test: kccevent
         ......................... SERVER passed test kccevent
      Starting test: systemlog
         ......................... SERVER passed test systemlog
      Starting test: VerifyReferences
         ......................... SERVER passed test VerifyReferences

   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom

   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom

   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom

   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom

   Running partition tests on : smallbusiness
      Starting test: CrossRefValidation
         ......................... smallbusiness passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... smallbusiness passed test CheckSDRefDom

   Running enterprise tests on : smallbusiness.local
      Starting test: Intersite
         ......................... smallbusiness.local passed test Intersite
      Starting test: FsmoCheck
         ......................... smallbusiness.local passed test FsmoCheck