Re: Win32::TieRegistry with remote CUser?

HKEY_CURRENT_USER will never be accessable to you remotely. What you can do though is go through HKEY_USERS and remove the data from there. If it's something that you're afraid that HKCU will save back to HKU, you can have your script do what it needs to remotely, then copy a script to the machine and put an entry in HKU\.Default\Software\Microsoft\Windows\CurrentVersion\RunOnce and it will be run for each user who logs on to that machine. Might be a better way of approaching it if multiple people log on to one machine, and you don't want to itterate through all the users hives yourself.

Personally, I'd give everyone admin rights. From personal expierence, the time it takes to fix it if they break it is much less than the time it takes to do the piddly things you have to do for them.. and the time it takes to work around them not having admin rights.

Just my .02
Rich

Comment on Re: Win32::TieRegistry with remote CUser?

Replies are listed 'Best First'.
(tye)Re2: Win32::TieRegistry with remote CUser? by tye (Sage) on May 25, 2001 at 22:44 UTC
HKEY_CURRENT_USER will never be accessable to you remotely. I've been getting at HKEY_CURRENT_USER remotely just now while testing. With noone logged in, it was the registry of a user that a particular service runs under. When I logged in, the remote access switched to using my "user registry" (after I reopened). - tye (but my friends call me "Tye")	[reply]
Re: Re: Win32::TieRegistry with remote CUser? by the_slycer (Chaplain) on May 25, 2001 at 22:37 UTC
Ah.. Everybody Admin rights in a company with 30000 users scares me ;-) I admit I never thought of running it through Users, guess I'd do it for each SID in that case. That may be the way to go. Thanks.	[reply]
Re: Re: Re: Win32::TieRegistry with remote CUser? by rchiav (Deacon) on May 25, 2001 at 23:15 UTC
shrug There's 50,000 people here with admin rights. We'd need twice as many desk side support people to handle things if they didn't have admin rights. I just don't think it's cost efficient. *addition:* Each person has admin rights to only their own machine. And only administrators can log on locally. So only the user(s) of that machine can log on locally. Rich	[reply]