![]() 'Rename-Computer' seems to work even if executed from a windows 7 box. To fix the issue, close your existing command window (it’ll retain the old path), and go to your Environment Variables in advanced system properties. NETDOM works too, but I like Rename-Computer better because NETDOM is only included in Windows Server installations. Turns out the problem is related to the path variable! Sometimes though, especially after installing the Windows Support Tools on a server, you can get the following error when running netdom (and other system tools) : The procedure entry point I_NetNameValidate could not be located in the dynamic link library NETAPI32.dll. Using WMIC may come in handy if you need to script the renaming of several machines or just want show off your skills to coworkers. You may find the Netdom method more user friendly if you are just renaming one system. Rather than searching my documentation to find the FSMO role holders, it’s easier to log on to a server and run “netdom query fsmo” in a command prompt. Netdom can do the same thing Don’t forget that you can also rename a computer using Netdom. I manage and am responsible for Active Directory for a number of customers, both public and private sector. ![]() Yay, it’s time for another technical post!
0 Comments
Leave a Reply. |