I am not able to run the admin tools for domain management tasks as an
administrator. I am able to launch the tools but they don't us the
credentials I specify. For instance: I right click AD Users and Computers,
click runas and specify domain admin credentials. The mmc comes up and
states "MMC could not create the snap-in". This is really bad because I
can't user any of the admin tools. Does anyone know how to fix this?

Windows Connected

Windows Vista Tip: Run as administrator
Today, December 01, 2006, 2 hours ago | Josh
Now that you have begun your Windows Vista testing you may find that you are
struggling a bit with performing remote admin operations on your Windows
Vista workstation like you used to on Windows XP. In Windows XP right
clicking on a shortcut in the start menu and selecting "Run as" would always
prompt you for the credentials you wanted to use to perform an operation. In
Windows Vista if you are a local administrator on the workstation the default
behavior doesn't prompt you for credentials, it presents with what is called
a Consent UI. Basically it makes the assumption that since the ID that you
are logged in with is an admin on the local workstation that the admin
operation that you are about to perform just needs your full token.

This assumption can be false in companies that have adopted the best
practice of maintaining a separate ID to perform administrative operations.
So even though you are an admin on your workstation your logon account has no
real rights to your domain. Here is a quick way to change the behavior of
that prompt to revert it to something more like Window XP.

Step 1.) Launch GPedit.msc with administrative rights.

Step 2.) Browse to Windows Settings | Local Policies | Security Options

Step 3.) Scroll down to User Account Control: Behavior of the elevation
prompt for administrators in Admin Approval Mode and double click

Step 4.) Change this value from Prompt for Consent to Prompt for Credentials

This will make every admin operation prompt you for credentials while it is
great if you do a lot of remote operations it can become tedious if you are
performing a lot of local admin operations. Additionally, if the process you
are running requires both local admin and remote admin rights you will need
to make sure that your admin account for the remote operation is also an
admin on your workstation as well.

Bonus Tip: If your machine is a member of the domain and you are trying to
use a local admin account in a credentials prompt you can put .\ in front of
the ID and the domain will automatically change your local workstation.


"Brandon" wrote:

> I am not able to run the admin tools for domain management tasks as an
> administrator. I am able to launch the tools but they don't us the
> credentials I specify. For instance: I right click AD Users and Computers,
> click runas and specify domain admin credentials. The mmc comes up and
> states "MMC could not create the snap-in". This is really bad because I
> can't user any of the admin tools. Does anyone know how to fix this?
>
>
>

Hi, i have exactly the same problem and the solution diden't work for me.
I'm a domain admin but i can't run "Active directory users and computers"
with the error "MMC cannot create the snap-in".

any ideias ?

Regards

Nuno

"Stuart [MVP]" wrote:

> Windows Connected
>
> Windows Vista Tip: Run as administrator
> Today, December 01, 2006, 2 hours ago | Josh
> Now that you have begun your Windows Vista testing you may find that you are
> struggling a bit with performing remote admin operations on your Windows
> Vista workstation like you used to on Windows XP. In Windows XP right
> clicking on a shortcut in the start menu and selecting "Run as" would always
> prompt you for the credentials you wanted to use to perform an operation. In
> Windows Vista if you are a local administrator on the workstation the default
> behavior doesn't prompt you for credentials, it presents with what is called
> a Consent UI. Basically it makes the assumption that since the ID that you
> are logged in with is an admin on the local workstation that the admin
> operation that you are about to perform just needs your full token.
>
> This assumption can be false in companies that have adopted the best
> practice of maintaining a separate ID to perform administrative operations.
> So even though you are an admin on your workstation your logon account has no
> real rights to your domain. Here is a quick way to change the behavior of
> that prompt to revert it to something more like Window XP.
>
> Step 1.) Launch GPedit.msc with administrative rights.
>
> Step 2.) Browse to Windows Settings | Local Policies | Security Options
>
> Step 3.) Scroll down to User Account Control: Behavior of the elevation
> prompt for administrators in Admin Approval Mode and double click
>
> Step 4.) Change this value from Prompt for Consent to Prompt for Credentials
>
> This will make every admin operation prompt you for credentials while it is
> great if you do a lot of remote operations it can become tedious if you are
> performing a lot of local admin operations. Additionally, if the process you
> are running requires both local admin and remote admin rights you will need
> to make sure that your admin account for the remote operation is also an
> admin on your workstation as well.
>
> Bonus Tip: If your machine is a member of the domain and you are trying to
> use a local admin account in a credentials prompt you can put .\ in front of
> the ID and the domain will automatically change your local workstation.
>
>
> "Brandon" wrote:
>
> > I am not able to run the admin tools for domain management tasks as an
> > administrator. I am able to launch the tools but they don't us the
> > credentials I specify. For instance: I right click AD Users and Computers,
> > click runas and specify domain admin credentials. The mmc comes up and
> > states "MMC could not create the snap-in". This is really bad because I
> > can't user any of the admin tools. Does anyone know how to fix this?
> >
> >
> >

OK I made these changes, it prompted me for the credentials which I entered,
then it still came up with the message "MMC could not create the snap-in".
So what do I do now? Thanks for any help...this is really frustrating!

"Stuart [MVP]" wrote:

> Windows Connected
>
> Windows Vista Tip: Run as administrator
> Today, December 01, 2006, 2 hours ago | Josh
> Now that you have begun your Windows Vista testing you may find that you are
> struggling a bit with performing remote admin operations on your Windows
> Vista workstation like you used to on Windows XP. In Windows XP right
> clicking on a shortcut in the start menu and selecting "Run as" would always
> prompt you for the credentials you wanted to use to perform an operation. In
> Windows Vista if you are a local administrator on the workstation the default
> behavior doesn't prompt you for credentials, it presents with what is called
> a Consent UI. Basically it makes the assumption that since the ID that you
> are logged in with is an admin on the local workstation that the admin
> operation that you are about to perform just needs your full token.
>
> This assumption can be false in companies that have adopted the best
> practice of maintaining a separate ID to perform administrative operations.
> So even though you are an admin on your workstation your logon account has no
> real rights to your domain. Here is a quick way to change the behavior of
> that prompt to revert it to something more like Window XP.
>
> Step 1.) Launch GPedit.msc with administrative rights.
>
> Step 2.) Browse to Windows Settings | Local Policies | Security Options
>
> Step 3.) Scroll down to User Account Control: Behavior of the elevation
> prompt for administrators in Admin Approval Mode and double click
>
> Step 4.) Change this value from Prompt for Consent to Prompt for Credentials
>
> This will make every admin operation prompt you for credentials while it is
> great if you do a lot of remote operations it can become tedious if you are
> performing a lot of local admin operations. Additionally, if the process you
> are running requires both local admin and remote admin rights you will need
> to make sure that your admin account for the remote operation is also an
> admin on your workstation as well.
>
> Bonus Tip: If your machine is a member of the domain and you are trying to
> use a local admin account in a credentials prompt you can put .\ in front of
> the ID and the domain will automatically change your local workstation.
>
>
> "Brandon" wrote:
>
> > I am not able to run the admin tools for domain management tasks as an
> > administrator. I am able to launch the tools but they don't us the
> > credentials I specify. For instance: I right click AD Users and Computers,
> > click runas and specify domain admin credentials. The mmc comes up and
> > states "MMC could not create the snap-in". This is really bad because I
> > can't user any of the admin tools. Does anyone know how to fix this?
> >
> >
> >

Ok, i got the answer, it worked for me:
http://winconnected.com/forums/4858/ShowThread.aspx

Regards.


"Debbie" wrote:

> OK I made these changes, it prompted me for the credentials which I entered,
> then it still came up with the message "MMC could not create the snap-in".
> So what do I do now? Thanks for any help...this is really frustrating!
>
> "Stuart [MVP]" wrote:
>
> > Windows Connected
> >
> > Windows Vista Tip: Run as administrator
> > Today, December 01, 2006, 2 hours ago | Josh
> > Now that you have begun your Windows Vista testing you may find that you are
> > struggling a bit with performing remote admin operations on your Windows
> > Vista workstation like you used to on Windows XP. In Windows XP right
> > clicking on a shortcut in the start menu and selecting "Run as" would always
> > prompt you for the credentials you wanted to use to perform an operation. In
> > Windows Vista if you are a local administrator on the workstation the default
> > behavior doesn't prompt you for credentials, it presents with what is called
> > a Consent UI. Basically it makes the assumption that since the ID that you
> > are logged in with is an admin on the local workstation that the admin
> > operation that you are about to perform just needs your full token.
> >
> > This assumption can be false in companies that have adopted the best
> > practice of maintaining a separate ID to perform administrative operations.
> > So even though you are an admin on your workstation your logon account has no
> > real rights to your domain. Here is a quick way to change the behavior of
> > that prompt to revert it to something more like Window XP.
> >
> > Step 1.) Launch GPedit.msc with administrative rights.
> >
> > Step 2.) Browse to Windows Settings | Local Policies | Security Options
> >
> > Step 3.) Scroll down to User Account Control: Behavior of the elevation
> > prompt for administrators in Admin Approval Mode and double click
> >
> > Step 4.) Change this value from Prompt for Consent to Prompt for Credentials
> >
> > This will make every admin operation prompt you for credentials while it is
> > great if you do a lot of remote operations it can become tedious if you are
> > performing a lot of local admin operations. Additionally, if the process you
> > are running requires both local admin and remote admin rights you will need
> > to make sure that your admin account for the remote operation is also an
> > admin on your workstation as well.
> >
> > Bonus Tip: If your machine is a member of the domain and you are trying to
> > use a local admin account in a credentials prompt you can put .\ in front of
> > the ID and the domain will automatically change your local workstation.
> >
> >
> > "Brandon" wrote:
> >
> > > I am not able to run the admin tools for domain management tasks as an
> > > administrator. I am able to launch the tools but they don't us the
> > > credentials I specify. For instance: I right click AD Users and Computers,
> > > click runas and specify domain admin credentials. The mmc comes up and
> > > states "MMC could not create the snap-in". This is really bad because I
> > > can't user any of the admin tools. Does anyone know how to fix this?
> > >
> > >
> > >

This TIP should also work, check with this link

http://windowsconnected.com/forums/thread/4671.aspx

But the major problem with the Run As option after changing it in the
Gpedit.msc, it keeps prompting us to enter the username and password
everytime when we do some administrative job, even if we are the adminstrator
of the desktop, but here if I plan to uncheck the UAC, & tried to run the Run
As option, the issue is there again, it will not prompt for us to enter
different credential, ... is there any solution to over come this issue.
--
We are responsible for what we do, No matter how we feel.


"nunoxf" wrote:

> Ok, i got the answer, it worked for me:
> http://winconnected.com/forums/4858/ShowThread.aspx
>
> Regards.
>
>
> "Debbie" wrote:
>
> > OK I made these changes, it prompted me for the credentials which I entered,
> > then it still came up with the message "MMC could not create the snap-in".
> > So what do I do now? Thanks for any help...this is really frustrating!
> >
> > "Stuart [MVP]" wrote:
> >
> > > Windows Connected
> > >
> > > Windows Vista Tip: Run as administrator
> > > Today, December 01, 2006, 2 hours ago | Josh
> > > Now that you have begun your Windows Vista testing you may find that you are
> > > struggling a bit with performing remote admin operations on your Windows
> > > Vista workstation like you used to on Windows XP. In Windows XP right
> > > clicking on a shortcut in the start menu and selecting "Run as" would always
> > > prompt you for the credentials you wanted to use to perform an operation. In
> > > Windows Vista if you are a local administrator on the workstation the default
> > > behavior doesn't prompt you for credentials, it presents with what is called
> > > a Consent UI. Basically it makes the assumption that since the ID that you
> > > are logged in with is an admin on the local workstation that the admin
> > > operation that you are about to perform just needs your full token.
> > >
> > > This assumption can be false in companies that have adopted the best
> > > practice of maintaining a separate ID to perform administrative operations.
> > > So even though you are an admin on your workstation your logon account has no
> > > real rights to your domain. Here is a quick way to change the behavior of
> > > that prompt to revert it to something more like Window XP.
> > >
> > > Step 1.) Launch GPedit.msc with administrative rights.
> > >
> > > Step 2.) Browse to Windows Settings | Local Policies | Security Options
> > >
> > > Step 3.) Scroll down to User Account Control: Behavior of the elevation
> > > prompt for administrators in Admin Approval Mode and double click
> > >
> > > Step 4.) Change this value from Prompt for Consent to Prompt for Credentials
> > >
> > > This will make every admin operation prompt you for credentials while it is
> > > great if you do a lot of remote operations it can become tedious if you are
> > > performing a lot of local admin operations. Additionally, if the process you
> > > are running requires both local admin and remote admin rights you will need
> > > to make sure that your admin account for the remote operation is also an
> > > admin on your workstation as well.
> > >
> > > Bonus Tip: If your machine is a member of the domain and you are trying to
> > > use a local admin account in a credentials prompt you can put .\ in front of
> > > the ID and the domain will automatically change your local workstation.
> > >
> > >
> > > "Brandon" wrote:
> > >
> > > > I am not able to run the admin tools for domain management tasks as an
> > > > administrator. I am able to launch the tools but they don't us the
> > > > credentials I specify. For instance: I right click AD Users and Computers,
> > > > click runas and specify domain admin credentials. The mmc comes up and
> > > > states "MMC could not create the snap-in". This is really bad because I
> > > > can't user any of the admin tools. Does anyone know how to fix this?
> > > >
> > > >
> > > >

Durqaprasad, put the Administrative rigths in the gpedit.msc just the way it
used to be. then fallow this
http://winconnected.com/forums/4858/ShowThread.aspx and it will work just
fine.



This TIP should also work, check with this link

http://windowsconnected.com/forums/thread/4671.aspx

But the major problem with the Run As option after changing it in the
Gpedit.msc, it keeps prompting us to enter the username and password
everytime when we do some administrative job, even if we are the adminstrator
of the desktop, but here if I plan to uncheck the UAC, & tried to run the Run
As option, the issue is there again, it will not prompt for us to enter
different credential, ... is there any solution to over come this issue.
--
We are responsible for what we do, No matter how we feel.

Hi,

I am already a administrator for the desktop, also I have already
registered the following registry keys for AD, but my problem is, when I goto
the user accounts, I disable the UAC, and then restart the machine, then I
login to the machine with a different credential, when I select run-as for
the AD, it will not prompt for me to enter elevated AD Credentials.

The reason for me to disable the UAC, is because, when I select MANAGE
option, or any other options which is used for Administrative, it keeps
prompting me for to enter the username and password.

Is there any option for me to disable the UAC, but when I forcefully select
Run As it should prompt me to enter the username and password.

With Regards,
Durgaprasad

"nunoxf" wrote:

>
> Durqaprasad, put the Administrative rigths in the gpedit.msc just the way it
> used to be. then fallow this
> http://winconnected.com/forums/4858/ShowThread.aspx and it will work just
> fine.
>
>
>
> This TIP should also work, check with this link
>
> http://windowsconnected.com/forums/thread/4671.aspx
>
> But the major problem with the Run As option after changing it in the
> Gpedit.msc, it keeps prompting us to enter the username and password
> everytime when we do some administrative job, even if we are the adminstrator
> of the desktop, but here if I plan to uncheck the UAC, & tried to run the Run
> As option, the issue is there again, it will not prompt for us to enter
> different credential, ... is there any solution to over come this issue.
> --
> We are responsible for what we do, No matter how we feel.
>
>