Windows 7 taskpad for resetting passwords

[ZeroHour]

Hi

I have got the admin tools to install to windows 7 and they seem fine but I cant get a custom mmc to load for users (delegation *seems* to be fine in ad)

They can load the ad users and computers but when they try to run my mmc an error "This function is not supported on this system" and I have no idea why.

All the mmc needs to do is allow staff to reset passwords from a buried OU down but I cant see where the problem is and that error is so useful...

 

Any ideas?

 

Cheers

[john]

Are you and Ric in connection over this as he's been searching for the answer to this since last week and we haven't solved it yet

[ZeroHour]

No but I didnt realise was getting the same error.

[chazzy2501]

NEVERMIND Edited September 16, 2010 by chazzy2501
I suck

[Ric_]

No but I didnt realise was getting the same error.

 

My problem is different. I don't want to install the 220MB .MSU file on each client so I've been trying to find a way around it.

 

It was nice and easy on XP... install adminpak.msi and then make a taskpad view in a MMC.

[ZeroHour]

My problem is different. I don't want to install the 220MB .MSU file on each client so I've been trying to find a way around it.

 

It was nice and easy on XP... install adminpak.msi and then make a taskpad view in a MMC.

 

You really have to use the MSU, suck it up

Did you get it to work with the MSU and taskpad?

[Ric_]

You really have to use the MSU, suck it up

Did you get it to work with the MSU and taskpad?

 

Erm... hang on... yes it does

[SYNACK]

My problem is different. I don't want to install the 220MB .MSU file on each client so I've been trying to find a way around it.(

 

Does it provide a helpful error as to which DLLs are missing if you just copy DSA.MSCacross from a machine with RSAT installed and try to run it on a fresh machine. I'd give that a go and maybe grab a copy of procmon and see what files it tries and fails to access on load, this should get you the dependencies (depends.exe from the Windows SDK may be able to extract them as well) then it is just a case of putting the DLLs in the right place and registering them. Could probably bundle the whole lot up into an MSI of your own with something like Winstall LE and just deploy that.

[Ric_]

@SYNACK: No useful error messages are given if you do that (I already tried!)