Domain login profile copy required
We have people who work remotely (Xp Pro) and connect up post login via a VPN connection. When a new user starts we need them to be able to log into the laptop as their new login without coming into the office/logging onto the network. We can establish a VPN under another user account to administer the computer. "Log on using dial-up connection" is not an option as we use 2 factor RSA token authentication and our VPN Client vendor does not support this method of authentication pre-login.
How do we get the users profile onto a machine? Is it possible to create a cached account on a local machine in the office and copy it across?
We cannot simply copy the users logon directory as we need the users cached password copied across as well. The account the user uses to authenticate must be a domain account and not a local one.
Suggestions please.
How do we get the users profile onto a machine? Is it possible to create a cached account on a local machine in the office and copy it across?
We cannot simply copy the users logon directory as we need the users cached password copied across as well. The account the user uses to authenticate must be a domain account and not a local one.
Suggestions please.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Oh, and this probably goes without saying, but I will anyway.....
You need to be connected to the domain, either via a post login VPN connection, or a live office network connection....
You need to be connected to the domain, either via a post login VPN connection, or a live office network connection....
ASKER
Thank you for the suggestion HTH. I suspect my requirements may not be clear. Your suggestion is a utility for copying the profile of a user (icons, desktop wallpaper etc), it does not look to include copying of the password (hash?) and SSID.
For Example
If you ran this utility on a machine domain "User A" had logged on to, copied the output via a USB pen drive onto a new machine domain "User A" had never logged onto using your own administrative login and then disconnected the machine from the network you would not be able to log in with domain "User A" cached authentication credentials.
In the scenario above a successful solution would be one that allowed me to log in locally as domain User A once disconnected from the network without ever previously logging in with domain User A credentials to the new computer.
For Example
If you ran this utility on a machine domain "User A" had logged on to, copied the output via a USB pen drive onto a new machine domain "User A" had never logged onto using your own administrative login and then disconnected the machine from the network you would not be able to log in with domain "User A" cached authentication credentials.
In the scenario above a successful solution would be one that allowed me to log in locally as domain User A once disconnected from the network without ever previously logging in with domain User A credentials to the new computer.
Not sure, but I do not see how this is possible. You add the computer to the network yes? And then you want an unknown user to be able to authenticate to the domain (offline)? Essentially it seems that this is what you are asking. Without a domain user profile on that machine, then logging on will create a temporary profile for that user. Once the computer is back on the domain, it will recognize the user as legitimate and then change the profile. In theory...
John? Any suggestions on this?
John? Any suggestions on this?
ASKER
John - you are a star! Points and gratitude to you sir!
HTH - thanks for your help. Johns suggestion allows me to cache the new users credentials on the new machine without ever logging on (via the Xp Gina) as them. I can establish a VPN connection as an administrative account post login and then "run as" the new user account which caches the domain login credentials locally so when the new user logs in (via the Xp Gina) off-line for the first time it works.
HTH - thanks for your help. Johns suggestion allows me to cache the new users credentials on the new machine without ever logging on (via the Xp Gina) as them. I can establish a VPN connection as an administrative account post login and then "run as" the new user account which caches the domain login credentials locally so when the new user logs in (via the Xp Gina) off-line for the first time it works.
ASKER
John - you are a star! Points and gratitude to you sir!
Johns suggestion allows me to cache the new users credentials on the new machine without ever logging on (via the Xp Gina) as them. I can establish a VPN connection as an administrative account post login and then "run as" the new user account which caches the domain login credentials locally so when the new user logs in (via the Xp Gina) off-line for the first time it works.
Johns suggestion allows me to cache the new users credentials on the new machine without ever logging on (via the Xp Gina) as them. I can establish a VPN connection as an administrative account post login and then "run as" the new user account which caches the domain login credentials locally so when the new user logs in (via the Xp Gina) off-line for the first time it works.
"John? Any suggestions on this?"
In the example above, it would just be a profile with a matching name, but nothing in the registry for the cached domain credentials to be authenticated against under HKEY_LOCAL_MACHINE\SECURIT
"Without a domain user profile on that machine, then logging on will create a temporary profile for that user. Once the computer is back on the domain, it will recognize the user as legitimate and then change the profile. In theory..."
Without a cached account to authenticate, they shouldnt ever get logged on to even get a TEMP profile. So I think the rest of that train of thought is irrelevant, and not to mention that I think youre thoughts of it working that way, of being impossible, is spot on.
:^)
In the example above, it would just be a profile with a matching name, but nothing in the registry for the cached domain credentials to be authenticated against under HKEY_LOCAL_MACHINE\SECURIT
"Without a domain user profile on that machine, then logging on will create a temporary profile for that user. Once the computer is back on the domain, it will recognize the user as legitimate and then change the profile. In theory..."
Without a cached account to authenticate, they shouldnt ever get logged on to even get a TEMP profile. So I think the rest of that train of thought is irrelevant, and not to mention that I think youre thoughts of it working that way, of being impossible, is spot on.
:^)
Yes, you can copy the profile with this utility:
http://www.microsoft.com/downloads/details.aspx?familyid=ed182a96-f3a6-4fdd-862b-1ae03dc130c1&displaylang=en
HTH