Hello Ashenafi,
For SQL move start here: http://support.microsoft.com/kb/269196
Don't know if renaming SQL is a good solution: http://msdn.microsoft.com/en-us/library/ms143799.aspx
http://msdn.microsoft.com/en-us/library/ms143799(SQL.90).aspx
I would ask this in a SQL NG, there are some but start here: microsoft.public.sqlserver.server microsoft.public.sqlserver.setup microsoft.public.sqlserver.tools
For file server use the FSMT: http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfsc.mspx
A file server rename is not that kind of problem. But how does you connect your users, when not using mappings or logon scripts?
Best regards
Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
[Quoted Text] > I am about to complete the user and computer account migration form NT > 4.0 domain to a different Windows 2003 AD Domain. I am trying to setup > a lab environment to test migration of Domain resource objects like > SQL servers, File share servers and other application servers. The > problem is the name of these servers will be changed to the new/target > domain naming convention during the migration. I would like to mention > that users are connected to the databases using ODBC connection and we > don’t use DFS to access shares nor do we use login scripts to map to > network derives for shares. > > How should I proceed? Especially how can I prevent access issues > coming with change of name of servers? What should be the best > approach? > > Regards > > Ashe > > http://forums.techarena.in>
|