A TechRepublic member emailed me almost a situation that arose in which a machine was on a domain but could only get to the domain when connected to the VPN. The reader could log on every bit the domain ambassador only non the regular user because the domain admin had his credentials cached on the machine. It turns out the VPN wasn't gear up upwardly. The other problem was that the user isn't e'er going to exist on the domain or on a network.

My answer is that the credentials demand to exist cached; otherwise, the user won't exist able to log in when he is not on the domain. Just how can this be done when the machine is not currently on the domain or the VPN? I came up with a nifty petty trick to get those precious credentials cached.

Before following my instructions, you need to consider these requirements in order for the trick to work: The domain admin credentials must accept been previously cached on the computer. With the credentials cached, it is possible to log on to the machine.

  1. Log on and connect the VPN and so the user can exist authenticated.
  2. Navigate through the Start Menu to Notepad, concord down the Shift key, and right-click the Notepad entry.
  3. Select Run As Dissimilar User from the drop-down list.
  4. Enter the domain credentials for that user.
  5. Create a dummy file in Notepad and save the file.
  6. Log out equally the domain admin.
  7. Log in with the user using the domain credentials.

Yous should exist able to log in as that user without having to be on the domain or the VPN. I highly recommend you set up that user so the VPN comes upward at boot. If this is not possible, you should make sure the credentials are cached.

Working on a domained environment can exist both a blessing and a curse. For the near office, it will make life much easier, simply when issues ascend, brace yourself for a claiming.

Enquire Jack: If you have a DIY question, e-mail it to me, and I'll practice my all-time to answer it. (Read guidelines about submitting DIY questions.)