BradP.

In general terms, how did you get C# to get access to this info?

Whenever I'm having problems with a proprietary app, I do the following: Check application event log for errors related to the program. Browse to the program's directory and look for any file with a .log extension. Open them and look for errors. Check the manufacturer's website in the support section. If it's a common problem, they'll have it listed there.

The only non-'merican team that can go to the Series that I know of is the Toronto Blue Jays. There was a Montreal Expos as well, but I think they've gone away. *not a baseball expert*

I use a vbscript that maps printers by computer OU.

What about taking ownership of its parent and checking the "Replace owner on subcontainers" box? Maybe Windows is smart enough to propagate it.

Try this: Browse to the file in the command prompt. DIR /X REN stupidfileshortname test DEL test

The change name right is a local right on the computer, regardless of the computer's domain membership.

I've had similar problems happen when the file's short name got screwed up, and it seems to only happen in student directories for me as well. What are they doing, anyway? Try this: In command prompt, browse to the parent directory of the file or directory giving you the problem. Type dir /x. The x switch will show you the short name (e.g., vssdoc~1.doc). Then type del shortnameoffile. That should get rid of it.

The way I thought it worked is that any user account can add up to 10 computers to a domain, if they need to add more they will need to be a member of the account operators group or have permissions delegated to them in AD. I would guess the change name button is greyed out because they are not local administrators. Perhaps you should create a "tech" group with all of your IT staff in the group and add it to the local administrators groups on your PCs (doable through restricted groups in group policy or manually). MS article

Using this document: MSDN article I came up with the following: 1) In regedit, under HKEY_CLASSES_ROOT, create a key called .pdf and change the default value to myAcrobat. 2) Create another key called myAcrobat. Create a subkey called shell. Create another subkey under shell named Open. Create a subkey under Open named command. Change command's default value to the UNC path to acrobat's exe. 3) Export the myAcrobat and .pdf keys to .reg files and distribute. I have no idea of the ramifications if you ever needed to install Acrobat on the computers you changed the keys to, though.

This should set the default printer: Set objNetwork = WScript.CreateObject("WScript.Network") objNetwork.SetDefaultPrinter "\\SERVER\PRINTER"

I don't know if this helps, but I've found that if you have a mandatory profile and apply Group Policy, the Group Policy will not apply unless the user is an administrator on the local computer. GPResult will say that it applied the policy, but the settings will not apply. Related to this, I've also found that if the profile that you move to the default user on a local computer had a Group Policy applied to it(domain or local), then the policy will continue to apply to any profile that gets created from the default user, and GPResult will never show it being applied! I've made a point for the technicians to only copy the local administrator's profile (no domain GPOs) before any local GPO is created if they want to tweak the default user profile settings. Otherwise we end up with "ghost" group policy settings being applied. Maybe what you're experiencing is related to either of those situations.