Tuesday, March 01, 2011 4:03 AM
I've been following the guide found here: http://go.microsoft.com/fwlink/?LinkId=134770 but when it came time to import, my 2008r2 server acts like it has never heard of the migration tool before. I tried following the netsh instructions found elsewhere on the web but it didn't really work for me, so I decided to just try smig. What I get specifically is:
PS C:\Users\administrator.MYDOMAIN> Import-SmigServerSetting -featureid DHCP
The term 'Import-SmigServerSetting' is not recognized as the name of a cmdlet, function, script file, or operable progr
am. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:25
+ Import-SmigServerSetting <<<< -featureid DHCP
+ CategoryInfo : ObjectNotFound: (Import-SmigServerSetting:String) , CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
I need to completely replace a Windows 2008 (x86) domain controller with a pair of Windows 2008R2 controllers. There is a lot of customisations to the server (like how scripting is handled) so I'm proceeding carefully. I've got DFS, Netlogon etc working on the new controllers, so I'm just moving DHCP across next. Any advice on that would be appreciated.
- Changed Type Miles ZhangModerator Monday, March 07, 2011 1:47 AM
Wednesday, March 02, 2011 9:34 AMModerator
Thanks for the post.
Before you run the Import-SmigServerSetting, Export-SmigServerSetting, or Get-SmigServerFeature cmdlets, verify that during migration, both source and destination servers can contact the domain controller that is associated with domain users or groups who are members of local groups on the source server.
Please also refer to the following article:
Hope this helps.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
- Marked As Answer by Miles ZhangModerator Monday, March 07, 2011 1:50 AM
Sunday, April 01, 2012 11:34 PM
This issue might occur if you have not added the migration snapin into he powershell.
Run the following command on the powershell and try again.
Monday, July 16, 2012 3:53 AM
open up a powershell session with elevated rights - type following (without quotes) and try the command again
Thursday, February 21, 2013 3:48 PMI am having the same problem. I voted the above two as "helpful". But above command only good for one session. If you restart your Windows 2008 R2 server it will be lost. Then you will encounter the same problem again. I am working on some permanent fix too. will post when I found it. Any one have a light please shed.