I speak from experience with a large laptop user base who are out of the office quite a lot.
If all you have in your organisation are desktops then yes forcing the discovery should be enough.
Sorry for not replying sooner - hectic week back after a week off!!
I've only done some very quick testing so far but it seems to do what it says on the tin.
The interface isn't pretty and there are not many options.
I will let you know once I have done more testing but so far I have been...
Providing all the PC's already report to the existing server you can just change the distribution policy for the pc's and set it to the new server (as cmeagan656 said).
For this to happen though all clients will need to have the phone home server set to the current server. If not you can roll...
Last thing to try and then I'm out of ideas.
In the registry browse to:
HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\SERVICES\MNMDD
make sure/change the "start" key is set to "1"
if not final thing....
....long shot but http://support.microsoft.com/default.aspx?scid=kb;en-us;q175956
It also relies on Plug and Play and users need read and write access to Nmcom.dll.
It has been known previously that permissions can get "screwed" on the file for some reason.
Try these steps.
* Open the Services window and ensure that both NetMeeting Remote Desktop Sharing and Plug and Play...
You could always look at scheduled tasks (under control panel)
they will allow you to schedule a task to start every-time the system starts up - you can also select the user account to run it under.
Have a look but let me know if you need any more details.
I'm on leave this week but when I get back I will be using the kernel tool (bought it just before my leave started) to do a small migration.
When I have used it I can give you a bit more information on it.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.