I am deploying Windows XP workstations on an AD 2000 domain. Our current method gives users elevated right to update the registry on the Windows 2000 Professional workstations.
I do not want to use this same method with XP.
The login script uses reg files and KIX scripts to update the registry and I would like to know the best way to have these scripts executed on XP service pack 3.
Many thanks in advance.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Arnold,
Thanks for you inpout. The users are not changing the registry. We have numerous locations which require different settings for applications. The login script parses a text file for the relevant location specific information and then updates the registry. Elevated user permissions were given in the Windows 2000 environment and we want to avoid that for Windows XP.
Is the need to adjust the registry part of a specific application's requirement?
Here is a link to an EE question that deals with adjusting permissions on a registry key:
http://www.experts-exchang
I.e. add a group to the key (startup script which runs with system level rights) and then when the user of that group logs in and your script tries to alter something within the key, it will work.
The startup will likely work for HKLM. Is the registry alteration system wide or is it a per user change/rule?
What about File DSN's?
Or Just use Startup Scripts......
Assign computer startup scripts
http://technet.microsoft.c
Thanks for all of the comments. All differences are by location and not user. Computers are not setup by location OU.
Users are group in OU according to job function. A text file is used to store the location specific variables. The login script then parses the text file and applies the values to the registry.
We like the use of the text file as it allows easy changes of the location variables.
As for the startup scripts, how are these different from the login script we are already using?
The login script does the same thing, the difference between a login script and a startup script is when it is executed, how often it is executed and with whose credentials it runs.
The startup script will only run once at startup.
It will run with system credentials.
Organizing the AD into OUs that designate a location, is a simpler and cleaner approach. Since then you can set registry parameters through GPO.
What is the basis on which the location is determined?
Lets say you have site a and site b. How is the login script that processes the text file that contains information about site a and site b differentiates and applies the variables from site a and not site b?
How does the script determine which location the system is in?
Reread your earlier post and you have OUs for users. The startup script will have difficulties because at the time of processing, there is no user.
You better off, adjusting the permissions on the:
HKLM\software\microsoft\ms
HKLM\software\odbc\odbc.in
To allow domain user modification rights and remaining with the login script.
Business Accounts
Answer for Membership
by: arnoldPosted on 2009-02-05 at 07:34:56ID: 23560272
Depending on which registry keys you are trying to push, HKLM or HKCU, you might be able to push them through the GPO?
Why would a user need to change registry? Alternatively, you can alter the permissions on a specific registry hierarchy to allow users to make alterations to this key only without affecting other keys.
Registry entries, I think are under the security computer settings\windows settings\security. The security adjustment on the keys, are more involved. You would likely need to have a startup script that will run with System credentials and would adjust the security permissions on the key. Have not tried and have not looked on whether such a script is available.