Re: Server 2008 adprep

The difference relates to what the default is:

in Windows 2003, when logged on with an adiministrative user account, all programs (including cmd.exe) run with full administrative privileges by default
in Windows Vista and 2008, all programs (including cmd.exe) run with "restricted" - i.e. normal user - privileges by default

The check box "Run this program with restricted access" in the Windows 2003 Run As dialog is a way, as an administrator, to run a single program with "restricted privileges" if you want to. This check box only has meaning when you use the Run As dialog. Unless you use the Run As dialog, all programs will run as if this check box is NOT Checked.

With Vista and Server 2008, the situation is reversed. All programs will run "restricted" unless you launch them "elevated" by using the Run As Administrator context menu item.

The other difference is that with the Windows Server 2003 (or XP) Run As dialog, you can specify a different user account for the program to execute with (select the "The following user:" radio button), even if you are logged on with an administrative user account. With Vista and Server 2008, if you are logged on with an administrative user account, you don't get that option via the Run As Administrator context menu item. If you are logged on with a non-administrative user account, the Run As Administrator dialog forces you to specify the user credentials to run the program with.

In Windows 2003, when you log on with an administrative user account only one security context is created for that Windows Session and this one has the full administrative rights and permissions. The Run As... context menu item provides a way to launch a particular program in a different security context.

When you log on with an administrative user account in Vista or Windows Server 2008, two security contexts are created for the Windows Session:

a "normal user" security context that has the rights and permissions assigned to the user, but with the "administrative" rights and permissions removed - this is the default security context for programs launched by that user

an "elevated" security context that has all the rights and permissions assigned to the user - this security context is only used when a program is launched using the "Run as Administrator" context menu item


--
Bruce Sanderson
http://members.shaw.ca/bsanders

It is perfectly useless to know the right answer to the wrong question.



"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message news:ff16fb668cdd18ca4acca6819ef3@xxxxxxxxxxxxxxxxxxxxxxx
Hello richardb,

If you open it with run as you also can see that even if it is the administrator a checkmark is set for "Run this program with restricted access". So what is the difference, except the naming, between "run as" and "run as administrator"? The link does not say anything different then i said.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

"run as" in ws03 is not the same as an elevated command prompt in
vista /ws08. see
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1018226&SiteID=1
for additional information.

Nevertheless I tried run as with my schema admin account with the same
result.

Best regards
Richard
"Meinolf Weber" wrote:

Hello richardb,

Start, programs,accessories, rightclick "commandprompt" and you have
RUNS AS.... available.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Thanks for the quick reply.

AFAIK elevated command prompts are not available in WS03...

Have a look at your Vista DVD: /sources/adprep
You will find Schema Version 39 needed for Bitlocker support and
probably
other things that i don't know in detail.
Best regards,
Richard
"Meinolf Weber" wrote:
Hello richardb,

Did you run it from a elevated command prompt? To open an elevated
command

prompt, click Start, right-click Command Prompt, and then click Run
as administrator.

http://technet2.microsoft.com/windowsserver2008/en/library/aa923ebf
-d e47-494b-a60a-9fce083d2f691033.mspx?mfr=true

NEVER heard from a Schema update that comes with a workstation
operating system like Vista, please can you clarify this.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties,
and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Hi all,

another one of my strange problems:

I have one DC - Windows Server 2003 R2 - and want to add a Windows
Server 2008 DC. When I run adprep /forestprep on my "old" DC the
server shows a blank line in the cmd window. (Now after 6 days
looking at this blank line I canceled this with Ctrl+C)

- I tried both adprep from the x86 and x64 discs (looks like they
are
the
same)
- Oh yes, my AD works fine - I successfully extended my schema to
Version 39
(as included on the Vista RTM CD) that moment on the same
server...
- I tried copying the adprep-Folder to my local disk and removing
the
"read-only"attribute
Any idea how to extend my schema?
Richard



.