server is win2008 enterprise SP2 x86
WSUS 3 SP2 , all hardware settings are good
this is strange since I connect to myservername with my username which has all the necessary credentials (ent admin) and start and run WSUS normally.
EminentWare can see my domain structure completely, even trusted domains but cant get my WSUS configurations (updates, groups, etc)
Could WSUS be using another user (some service username) aside from what I log on with? edit:just checked, using system and network service.
EminentWare.datagrideservice.exe is using ewdgssvc32-14322 username.
The Extension Pack uses the account credential configured in the Credential Ring for the WSUS Server; this credential and password was assigned to the WSUS Server during installation of the Extension Pack. From EminentWare System Configuration | Security and User Setup, select the Credential Rings tab, select the Credential Ring (most likely the only one present is <Default>), and select the Credential Ring Wizard from the actions pane or context menu. Advance one screen to the rules assignment screen and determine which credential is being used for the WSUS Server. Change this, if necessary, by assigning an alternate credential, or adding additonal credentials on the previous screen.
Hi nassimjd,
In addition to what Lawrence posted, you will get the 'Request for principal permission failed' if the account you are using is not a member of the 'WSUS Administrators' group on the WSUS server.
John
Thank Lawrence. actually I had done that several times but at no avail, I had added myself as an EminentWare Enterprise admin in the default credential ring.
by the way I think WSUS should be called the extension to EminentWare and not EminentWare the extension to WSUS. Very well done "Extension". Just if things were a
bit more evenly devided --> everything is under the action menu and the rest :file, help, view,... are there for aesthetics,,,,, but overall it deserves lots of thumbs up.
Hi jmarchesini
Thanks for the tip, that did it, solved the problem, now all updates and groups are loaded. The WSUS Admins group was EMPTY.
Thanks to everyone.
nassimjd:Server: MYSERVERNAMEMessage: Exception occurred at 12/14/2009 10:40:56 AM: Request for principal permission failed. WSUSConnection::Unable to connect to the WSUS Server (MYSERVERNAME) using the account: MYDOMAIN\MYUSERNAME Request for principal permission failed.server is win2008 enterprise SP2 x86 WSUS 3 SP2 , all hardware settings are good this is strange since I connect to myservername with my username which has all the necessary credentials (ent admin) and start and run WSUS normally.EminentWare can see my domain structure completely, even trusted domains but cant get my WSUS configurations (updates, groups, etc)Could WSUS be using another user (some service username) aside from what I log on with? edit:just checked, using system and network service.EminentWare.datagrideservice.exe is using ewdgssvc32-14322 username.
nassimjd:
Server: MYSERVERNAMEMessage: Exception occurred at 12/14/2009 10:40:56 AM: Request for principal permission failed. WSUSConnection::Unable to connect to the WSUS Server (MYSERVERNAME) using the account: MYDOMAIN\MYUSERNAME Request for principal permission failed.
server is win2008 enterprise SP2 x86 WSUS 3 SP2 , all hardware settings are good this is strange since I connect to myservername with my username which has all the necessary credentials (ent admin) and start and run WSUS normally.
I am getting a similar message when I am trying to run the Server Publication Verification wizard. Using credentials that are in the credential ring, I have even added that domain user to the WSUS Administrators group on the WSUS server, but to no avail. I am thinking it may either be services on the WSUS server or some GPO that is being applied incorrectly. I have the downstream WSUS server able to run the SPVW just fine using the same credentials. Wish I could come up with a solution. I will keep plugging away and let you know the solution (if any) that I find.
Any other suggestions?
This is often related to UAC.
It could also be related to some registry permissions.
Please send a email to Customer Support with your availability and we will schedule a webmeeting and get you fixed up.
This resolved the issue for me thanks a bunch!!!
That resolved my issue as well! Thanks!
