I am currently migrating an SBS 2003 server to new hardware, but I've run into an issue creating an alias on the new server that will effectively point to the old server. This migration has successfully moved Exchange and Sharepoint services, but there are numerous objects that are still pointing to the old server's name, so an alias is the optimal solution. I've followed the TechNet document for this migration, got to the last few steps, and ran into this.netdom computername DestinationServer /addourceServer.domain.localCannot add alternate name...The error is:The parameter is incorrectI've looked all over for a few hours, but could not find a solution. As it stands now, the customer's Sharepoint service is not operatin correctly, so I need a fix fast. Any input would be greatly appreciated.

I have thethe exact same issue. As well, I am migrating a Small Business Server 2003 to new hardware with hopes of then upgrading to SBS2003 R2. I can't say that it has gone that well and with the this issus at the end on the migration I am at the end of my rope. The alias sounded like a great fix for redirected clients.... but here I am. *$%^ed. I've got 3 days to finish the migration before the magic 7 days is up, and their's no mail flowing. I have tried every combination of netdom commands i could come up with, buteverything ends up in " the parameter is incorrect" or "the syntax of the command is:" My usage: netdom computername clients-dc /add: clients-srv.theirdomain.local Any help or direction would be great! Oh, and I would suggest "NO MIGRATION OF SBS2003" The 43 page manual with the 5 day checklist just Isn't worth it.

Open up Active Directory Users and Computers and under computers delete the old server name (it should be disabled)