SBS2011 Migration CNAME not working for XP Clients

Just completed a 2003 SBS to 2011 SBS migration and almost everything is working

Old SBS was called SBSSEERVER
New SBS is called SBS2011

We have setup a CNAME in DNS to point SBSSERVER to SBS2011 which works fine with Windows 7 machines, but this will not work with XP Client which complain of a duplicate name

Any Idea's on this one.

Thanks
HBPROCKAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
HBPROCKConnect With a Mentor Author Commented:
I've just found this http://support.microsoft.com/kb/281308 not sure if it will work on 2011
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Why would you do that in the first place?

Philip
0
 
HBPROCKAuthor Commented:
As it's quicker and easy to do a migration rather than a swing migration to retain the name of the server. We need to have both names registered to dns and SMB so old plant machines can still find there files for workin on drawings etc as these are hard coded to a unc path . I.e \\sbsserver\plant1\drawings.....
0
SMB Security Just Got a Layer Stronger

WatchGuard acquires Percipient Networks to extend protection to the DNS layer, further increasing the value of Total Security Suite.  Learn more about what this means for you and how you can improve your security with WatchGuard today!

 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
The Microsoft method that we use for most of our migrations does not account for this at all.

The end result with this method is always a new server with a new name and all apps migrated over. We have done _a lot_ of migrations.

See: http://blog.mpecsinc.ca

There are lots of migration related posts.

Only in Jeff's Swing method when properly executed do you end up with the server sharing the previous server name.

The CNAME situation presents all sorts of security implications since you are trying to have one box impersonate another.

There is a migration guide on the blog, check it out.

Philip
0
 
HBPROCKAuthor Commented:
I accept what your saying and I have also purchased and followed the swing migration paths In the past. In this instance  we have migrated all the applications to the new server and most connections and machines use the full dns name which is causing us no issues and since the adjustment in the above articles the factory machines can now see there data paths and production can continue with no downtime. I guess this works for us in this particular case. As for the security not to sure on how this affects things in a locked down network? Are you saying that giving the server 2 alias it becomes a security risk? This then would also be the case if you gave it a second ip address
0
 
HBPROCKAuthor Commented:
Sorted it ourself as per the article
0
 
ktaczalaCommented:
why cname and not host(A) record?
0
All Courses

From novice to tech pro — start learning today.