Re: Ooooopppps. Rights not right...

No offense, but did you actually read the posts in this thread? Your solution
is neither correct nor is it even on target.

The problem was to do this by group membership and log on scripts. You
ignored that and answered a diffrent non-existant question. Quite thourough,
but not useful.

Charles, what you want to do is most certainly possible. The user acount
that is logging in does not have the rights, but that doesn't mean that you
can't do it.

Use a log in script to call a compiled file stored on a share . In the
compiled file (i would use c++) use the runas function of windows to run the
ipconfig under the context of another user that has the rights.

You don't have to do it with a compiled file, you could simply use the
command runas in the script, but that potentially exposes a username and
password.

""Rebecca Chen [MSFT]"" wrote:

> Hi Charlie,
>
> After my further research and long time test, I have confirmed that we are
> unable to specify different gateway according to the user group. This is
> because the classid is for per machine instead of per user. For example, if
> you have create two user classes, one is called student; the other is
> staff. There is a client machine called TEST1, if you set the classid for
> TEST1 to student, when whoever account you logged will get student IP and
> gateway. It is a same on the opposite, if a machine called TEST2 and its
> classid is staff, a student logon to this machine and will get staff IP and
> gateway. Actually, the machine gets the IP address and the gateway before
> the user logon dialog box prompt. It is necessary for you manually to
> specify which machines the students can use, and other for the staff in
> management level.
>
> After you manually specify the machines, you then can use classid to assign
> different gateway to the clients. This is can be done through my test. I
> understand your concern is that the student account cannot perform
> "ipconfig /setclassid "*" student" and get the access denied error, this is
> because you have assign the batch file via the logon script, the common
> user does not have the permission to execute this command. I have written a
> startup script contains the following command:
>
> ipconfig /setclassid "*" stu
> ipconfig /renew
>
> Put this bat file to the computer startup script in the local group policy.
> The script has successfully changed the classid to stu under system
> account. To assign the scrip to the computer startup script, please use the
> steps below:
>
> NOTE: Please create a batch file called test.bat under the folder
> c:\windows\system32\grouppolicy\machine\script\startup folder, which
> contains the following command:
>
> ===========================
> ipconfig /setclassid "*" stu
> ipconfig /renew
>
> ================================
>
> 1. Bring up the local group policy by keying "gpedit.msc"
> 2. Locate to Computer configuration\Windows Settings\Scrip\Startup
> 3. Assign the test.bat as the startup script.
> For more information about the startup script, please refer to the
> following article, the concept is the same in win2k3:
>
> Overview of Logon, Logoff, Startup, and Shutdown Scripts in Windows 2000
> http://support.microsoft.com/default.aspx?scid=kb;en-us;198642
>
> 4. Restart the machine and you will find the classid has been successfully
> set and the machine has get the new IP address according to the classid.
>
> If you sucessfuly perform the steps above, please then deploy the OU policy
> to the machines which you want to change the classid.
>
> I belive it helps.
>
> If you have any update or question, please feel free to post back.
>
> Best regards,
>
> Rebecca Chen
>
> MCSE2000 MCDBA CCNA
>
>
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
>
> =====================================================
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
>
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
.

Relevant Pages

  • Re: Ooooopppps. Rights not right...
    ... unable to specify different gateway according to the user group. ... because the classid is for per machine instead of per user. ... you have create two user classes, one is called student; ... Put this bat file to the computer startup script in the local group policy. ...
    (microsoft.public.windows.server.general)
  • Re: Xcopy not working in startup script
    ... This is a basic batch file script that I am ... deploying through group policy in the startup script to copy ... it works fine on it's own, but when deployed through group policy it ... the permissions of the computer object elsewhere in the domain. ...
    (microsoft.public.windows.server.general)
  • Re: Internetstreaming
    ... It won't work in IE without specifying the CLASSID for media player. ... You can script that, but IE doesn't support standards compliant object ... Got a update from windows update concerning mediaplayer 11, ...
    (microsoft.public.windowsmedia.player)
  • Re: Xcopy not working in startup script
    ... This is a basic batch file script that I am ... deploying through group policy in the startup script to copy ... I'm deploying it during the ... the permissions of the computer object elsewhere in the domain. ...
    (microsoft.public.windows.server.general)
  • Re: Power Management GPO?
    ... I suspect that the power management subsystem might not be started when the startup scripts runs or the SYSTEM context can't modify it, but I have some ideas about this and will do some testing later on today to work it out. ... I created a GPO and put the batch file in first as a startup script and when that didn't work I tried it as a logon script. ... A normal user can't change the power settings so a logon script like this won't work either. ... I can't remember if all power setting are per machine, but if some are per machine and some are per user then you could split it up into 2 scripts, one startup script and one logon script. ...
    (microsoft.public.windows.group_policy)