Search results for query: *

I'll be damned. It's working now. I swear I tried it 50 times and it didn't work. But, you're right. It does change the %username% variable to the name of the user name of the template account, but maintains the fact that it's a variable. When the account is copied, it replaces the variable...

Sounds to me like you don't have admin rights on that server. Do you have a trust relationship between the two domains? If so, add your domain's administrator group to the administrator group in the other domain.

The Microsoft answer is that there is no upgrade path from Windows 2000 Server to Advanced Server. According to them, you need to reinstall. Personally, I never upgrade an operating system. I look at it as a good opportunity for a fresh install.

Mapping a network drive assigns a drive letter to a folder on another machine. Some programs can't handle UNC (\\server\share) path names and therefore mapping a drive is required. In your situation, it doesn't sound like you should have to map a drive. Since the folder that you need to...

If you have physical access to the system, an IPCONFIG will give you the (internal) IP address. If you are behind a NAT device, the external IP seen will be the same for all internal clients. If you have the computer name, you can simply ping it to get the IP address. The WINS snap-in can be...

The %username% variable is taken from the Pre-Windows 2000 username field. That field is required when creating an account. It won't let you leave it blank.

You'll need to delete the WINNT\$NTServicePackUninstall$ folder to get rid of the archived files. Add/Remove Programs will uninstall the service pack. You don't want that.

Are you verifying the client time against the DC they're authenticating to, or against the PDC? The users having trouble sound like they are geographically separated, and possibly all in the same location. I would guess you've got a DC at their location. How's the time set there?

Does this happen shortly after users change their passwords? I've seen that issue when replication wasn't working properly. When passwords expired, users would change them and then attempt to log in before replication finished. They would authenticate against their old password and lock...

Thanks for the reply vbrocks. I don't think the problem is that someone used the template to setup an account. I've tried recreating it, but cannot get the %username% variable to remain a variable. As soon as the template is created and saved, the variable is converted to its associated name...

We have several "template" user accounts in Active Directory that we copy when creating new accounts. This has always worked just fine, but we've recently encountered a problem. In the past, we specified the Home Folder in the format: \\server\share\%username%. The %username% environment...