Manually user domain account to PC

June 25, 2010 at 11:51:04
Specs: Windows XP, 2g
Hey guys,

I'm running into a domain accoutn problem and need some educated opinions.

The company has its own private network. No VLANS, all physical connections(T1,T3, Microwave, etc.)

There is one main office and many spread out offices across the state. The main office has the domain server. Every employee has a domain account/roamingprofile. Any employee can log into any PC on the network and their roaming profile will be copied to that PC.

My problem:

My techs & I (workstation admins) deliver PCs to users at remote locations. After the PCs are setup and on the network the users login and their profile is downloaded to that PC. With alot of these sites being 50+miles away the first login usually takes an hour where my techs or myself will sit there and wait until the user has successfully logged in and we see a desktop and test if everything is working correctly.

To get around this, we previously would call the users, get their user names and passwords, and log them in here at our main office and let the profile download as our connection at the main office is lightning compared to the remote offices.

Recently, security has asked us to discontinue this practice as It could cause some problems in the future(which I completely understand).

My questions:

Is there a command or way to manually add a domain user account and profile to a PC without having to log them in using their user name and password? I have tried to simple copy their profile over "C:\documents&settings\"USERPROFILE" to new PC but first time they login in, it creates a "USERPROFILE."DOMAIN" folder that it uses instead of the one I copied over.

Ideally, I would like to simply image the PC here in my office, run a command to manually add the user account and download the profile. After that, take the PC out to the remote site have the user login(since the profile is already on the PC(login time goes from 1 hours to 2 minutes).

Also, I'm sure we use some kind of active directory system although im not very familer with active directory.

Thanks in advance,


See More: Manually user domain account to PC

June 28, 2010 at 09:35:00
I would setup a Domain Controller at each site with replication. This way they login locally and if the connection was to go down they can still login.

Report •

June 28, 2010 at 09:55:03
"Recently, security has asked us to discontinue this practice as It could cause some problems in the future(which I completely understand). "

Only problem with this procedure is if you don't set the users account to 'change password at next logon'.

"tried to simple copy their profile over "
You copied a local not a domain profile which is why it didn't work. Try coping a domain profile instead.

Given how your company is using the network I would suggest a redesign based on terminal services/citrix with thin clients at the far ends. more secure and easier to maintain/maximize your bandwidth between sites

Report •

June 28, 2010 at 10:10:05
Unfortunatly I would'nt be able to anything like that. To make a change like that on our network would take many channels to go though and probably wouldnt get OKed unless it was suggested by one of the upper IT managers. My group and I are but lowly Desktop Support Techs and can only use scripts, small progeams, or anything already avalible on the PCs/Servers/network.
Thanks for the suggestion though =)

Report •

Related Solutions

June 28, 2010 at 12:29:52
Well your biggest issue is you are transfering Roaming Profiles over a T1 which can be slow if the user has changed a lot of local files or local files that are large in size. If you localize these files to local domain controllers you will take the stress off your T1s but this requires a major change and should only be done by the higher ups.

You could suggest it to them (if they are open to employee suggestions) other wise there is very little you can do to fix it. You may want to setup Login Schedules for each employee so that they are not all logging on at once.

Report •

June 28, 2010 at 12:41:02
I recently (by accedent) found a way I can do this.

by running the command: systeminfo /s "computername"
it downloads the account of the user running the command to the remote PC. After running the command and the account is created on the remote PC I can now easily copy the profile from the server to the PC now without having them log onto it
using the following scenerio.

client old PC name: olddesky - at remote locationg
Client new PC: newdesky - at my office

1. I call the client and ask them to run command from commmand prompt:
systeminfo /s newdesky

2. copy their profile from server to new PC
xcopy /e \\CompServer\Client profile C:\document settigns\ClientProfile

This works BUT as it only downloads the account of the current user that runs the command, I still have to call the client and get them to do it.

Is it possible to run the systeminfo command as another user without having their password?

Report •

June 29, 2010 at 12:33:28
"Is it possible to run the systeminfo command as another user without having their password?"

No. You can use the RUNAS but it needs the users password.

What you could do is setup a script on every computer and use MS Scheduler to run the script after hours as an Administrator. This is a security issue though because now you are storing the an Administrator Password inside of a Batch file on every computer.

Best to have it as a part of their login script and yes it will be slow the first time they login but it would only be that first time.


We considered using Roaming Profiles at our office but decided against it for these same reasons and the fact you need disk space for storing them. Our solution was to not use roaming profiles and make a Home directory for every user. They store their files that they want to access from other computers in that directory. As for email, we setup an Exchange Server and with this we did not need roaming profiles. Just an Idea.

Report •

Ask Question