Actually the subject: Supermicro server, which is used as a terminal server, we change to a newer HP. Why did I need AD - I do not know, because It was done long before me, but now they set the AD task to remove, and leave the user settings so that they do not feel the painful transition to a new hardware. Now there are 115 users, most of which work remotely. Tell me, please, what can be done to transfer to a new server ?

PS: admt & usmt tried, but 1 works only with AD, and the second - only with local uchetka.

  • Thank you all for the answers. Solved this problem by manually creating new accounts. - goodwin
  • Is it possible to "manually" interrupt and transfer profiles? O_o - Aleksey Kirilenko

2 answers 2

The dsmode user command doesn't help anything.

The author of the question understands that when AD is deleted, if an attempt is made to create users, then the newly created users will still have a different UID, since Initially, the UID includes the domain SID.

Accordingly, already configured profiles in the terminal server will be unavailable.

AD set to simplify work with a large number of users and computers in the enterprise network (and a bunch of other lotions with settings, including work in the terminal). Do you really need to demolish it?

There is such a utility User Profile Wizard , read about it, like it can save your already created profiles in the terminal server.

  • Thank you for understanding. In fact, previously there were many users on the network and AD was set up to simplify administration and other "buns". Now the number of users has decreased and everything except our department and 2 more people are connected remotely via VPN. Therefore, I apologize for the inaccuracy of the first message: there are currently 57 people online. I coped with this task manually, and at the moment the transfer is almost complete. There are only a few users left who have not tried the new server yet. - goodwin
  • Therefore, I can not be sure that all the settings and the necessary files are located in the "usual" places. - goodwin
  • I ask you then to share your experience (if of course not lazily) and describe all the steps that transferred and what software was used where and when, what with passwords, UID users and their profiles on local computers and in terminals. In more detail. If not here (although I think it will be useful for others too), then on s_live sabak soap list.ru - Home
  • Immediately I apologize for such a long absence. At the request of Home, I tell you how I coped with the task. Since the time for resolving this issue was not enough, and searches on the Internet did not lead to anything, it was decided to carry out the transfer manually. Information that I needed to know: • account names; account passwords; • account settings; • necessary databases, user files, and other trifles. - goodwin
  • 1. Account names taken from the old server. Here, I think, it is not necessary to explain anything. Passwords to accounts. Since information security in many firms is paid little (or rather, “not paid at all”) attention, then our company was no exception. I remembered some passwords, as I repeatedly visited other offices and set up VPNs, Remote Desktops, etc; some users remembered their passwords; and those who did not remember their password took out the paperwork with the recorded ones or (like Zadornov’s: "but now they are ready ... just ready? Inhale!") asked the neighbors in the office - goodwin '10

Try Ideal Migration