Vista - Release date: adminpack for Windows Vista (build 6000)

Hi,
Apparently there is no way I can get the "Active Directory Users and
Computers" snap-in to work on Windows Vista.I have tried several suggestions
,( like using the admin pack from windows 2003 without service pack, changing
the installer file , etc .. )which all have failed.( other snap-ins do work,
like gpo managenement )
The error I get in ADUC is "MMC could not create the snap-in".

Apparently a new adminpack is ready to be released "soon "
Any idea when this Adminpack for vista will available ?
(without soon in it :-)
A workaround would also be great

Thanks for your feedback

Didier

No idea when we will see a new admin pack.

have you tried this to get the currently one installed?

http://windowsconnected.com/blogs/ni...7/11/3235.aspx

--
Josh
http://windowsconnected.com
"Didier.T" <DidierT@discussions.microsoft.com> wrote in message
news:C18B2A6A-E2DC-4EBD-AE7F-717A61A3BEA9@microsoft.com...
> Hi,
> Apparently there is no way I can get the "Active Directory Users and
> Computers" snap-in to work on Windows Vista.I have tried several
> suggestions
> ,( like using the admin pack from windows 2003 without service pack,
> changing
> the installer file , etc .. )which all have failed.( other snap-ins do
> work,
> like gpo managenement )
> The error I get in ADUC is "MMC could not create the snap-in".
>
> Apparently a new adminpack is ready to be released "soon "
> Any idea when this Adminpack for vista will available ?
> (without soon in it :-)
> A workaround would also be great
>
> Thanks for your feedback
>
> Didier
>

Josh,

Yes I have tried this, but it didn't work for Active directory users and
computers
In Vista Build 6000 , you can even install the admin pack of windows 2003
Sp1 without this trick

Thanks,

Didier

So here you go.
ADprop.dll and DSadmin.dll fail to register. Use regsvr32 to manually
register those DLL's, otherwise Active Directory Users and Computers (ADUC /
DSA.MSC) fails to load correctly with "MMC could not create the snap-in"1.
Install 2003 SP1 adminpak.msi - there will be no errors or warnings2. Under
Administrative Tools, attempt to load Active Directory Users and Computers,
Active Directory Domains and Trusts, etc.3. You will receive: "MMC could not
create the snap-in." 4. Close any of the snap-ins you tried to use.5. Copy
all text between [start copy here] and [end copy here] and save as
FIXADMINPACK.CMD6. Run the script with elevated credentials to
register all ADMINPACK DLLs. No restart required.6. Restart the previously
failing ADMINPACK snap-ins and they should behave normally. [start copy
here]regsvr32 /s adprop.dllregsvr32 /s azroles.dllregsvr32 /s
azroleui.dllregsvr32 /s ccfg95.dllregsvr32 /s certadm.dllregsvr32 /s
certmmc.dllregsvr32 /s certpdef.dllregsvr32 /s certtmpl.dllregsvr32 /s
certxds.dllregsvr32 /s cladmwiz.dllregsvr32 /s clcfgsrv.dllregsvr32 /s
clnetrex.dllregsvr32 /s cluadmex.dllregsvr32 /s cluadmmc.dllregsvr32 /s
cmproxy.dllregsvr32 /s cmroute.dllregsvr32 /s cmutoa.dllregsvr32 /s
cnet16.dllregsvr32 /s debugex.dllregsvr32 /s dfscore.dllregsvr32 /s
dfsgui.dllregsvr32 /s dhcpsnap.dllregsvr32 /s dnsmgr.dllregsvr32 /s
domadmin.dllregsvr32 /s dsadmin.dllregsvr32 /s dsuiwiz.dllregsvr32 /s
imadmui.dllregsvr32 /s lrwizdll.dllregsvr32 /s mprsnap.dllregsvr32 /s
msclus.dllregsvr32 /s mstsmhst.dllregsvr32 /s mstsmmc.dllregsvr32 /s
nntpadm.dllregsvr32 /s nntpapi.dllregsvr32 /s nntpsnap.dllregsvr32 /s
ntdsbsrv.dllregsvr32 /s ntfrsapi.dllregsvr32 /s rasuser.dllregsvr32 /s
rigpsnap.dllregsvr32 /s rsadmin.dllregsvr32 /s rscommon.dllregsvr32 /s
rsconn.dllregsvr32 /s rsengps.dllregsvr32 /s rsjob.dllregsvr32 /s
rsservps.dllregsvr32 /s rsshell.dllregsvr32 /s rssubps.dllregsvr32 /s
rtrfiltr.dllregsvr32 /s schmmgmt.dllregsvr32 /s tapisnap.dllregsvr32 /s
tsuserex.dllregsvr32 /s uddi.mmc.dllregsvr32 /s vsstskex.dllregsvr32 /s
w95inf16.dllregsvr32 /s w95inf32.dllregsvr32 /s winsevnt.dllregsvr32 /s
winsmon.dllregsvr32 /s winsrpc.dllregsvr32 /s winssnap.dllregsvr32 /s
ws03res.dll[end copy here]Try this,
--
Josh
http://windowsconnected.com

Now with NNTP goodness!

"Didier.T" <DidierT@discussions.microsoft.com> wrote in message
news:A585DFD2-FFF0-4982-867C-CE78D4CB7BD3@microsoft.com...
> Josh,
>
> Yes I have tried this, but it didn't work for Active directory users and
> computers
> In Vista Build 6000 , you can even install the admin pack of windows 2003
> Sp1 without this trick
>
> Thanks,
>
> Didier
>

Josh,

Thanks,
That worked !
Detail:
For a computer account this is ok
For an OU I still miss the group policy tab
But now if I select a user ( which is not the normal icon for user, infact
all icons are like text file icons , except OU's) , i still get an error on a
certain snap-in. ( probably the exchange one)
When I checked the system manager of exchange, I get the same error as for
ADUC .
Any idea which dll's I need to register to get the System manager working
again?

Thanks for your help

Regards,
Didier

On Wed, 22 Nov 2006 00:51:01 -0800, Didier.T
<DidierT@discussions.microsoft.com> wrote:

>Josh,
>
>Thanks,
>That worked !
>Detail:
>For a computer account this is ok
>For an OU I still miss the group policy tab
>But now if I select a user ( which is not the normal icon for user, infact
>all icons are like text file icons , except OU's) , i still get an error on a
>certain snap-in. ( probably the exchange one)
>When I checked the system manager of exchange, I get the same error as for
>ADUC .
>Any idea which dll's I need to register to get the System manager working
>again?
>
>Thanks for your help
>
>Regards,
>Didier
>
>
I've done this and it works fine, but I have no Terminal Server
Profile tab. Any way to get it to show?

Nope,

I have stopped using ADUC in Vista, for now...

Hi,

I have the same issue after I ran the dll from the kb/930056no

The icons in the results pane disappear after you click the pane.
The icons in the results pane are displayed as a Text File which I have no
way to tell if the user object is enable or disable.

Anyone knows if there is a fix?

Thanks.
Mugen


"gysgt_wong" wrote:

one of the minor notes in the KB article is, if you are running the 64bit
version of vista, in the command prompt you must be set to the WOW64
directory. when I reran this from that directory it started working.

However, now the GPO manger has the issue.

"Didier.T" wrote: