06-13-2012 06:23 AM
I'm running NG15SP1 on a Windows 7 Professional 64 bit PC - all updates installed.
When I first installed NG15, I did it under a different administrator account. Then I decided to align account names across 4 PCs on my LAN so I'm trying to run NG15 under a different administrator account. When I first got this problem, I uninstalled NG15 and reinstalled under the new account - no difference - same error. I have been unable to get any recovery points so I cannot restore.
Here's what happens when I run NG15:
"The current user 'MEMBERS-PC\Sys Admin' has read only priviliges and cannot make administrative changes.
Would you like to add priviliges for full control? Click No to continue in read only mode"
CLICK YES; UAC: "Allow changes?" CLICK YES
"ERROR: No mapping between account name and security IDs was done"
Click OK - error window is still there or there is an identical one right behind the first error window.
Click OK again - error window disappears and NG15 console opens in r/o mode.
Solved! Go to Solution.
06-13-2012 11:07 AM
From the start menu go to Programs\Norton Ghost. Right click on "Security Configuration Tool" and select "run as administrator".
In the top section click once to highlight the user, then in the bottom section chck the box for full control.
06-13-2012 05:20 PM
Thanks - that worked!
I'm still puzzled - my account and Administrators were both already marked "Full Control". Users was not full control so I gave it full control and it works. Shouldn't it have worked with my account (where I was running NG15) having Full Control.
Anyway, thanks again.
06-13-2012 06:41 PM
It should have worked fine without you doing anything if the new or changed user was a member of the administrator group.
But I think the permissions didn't carry over because of the space in your user name.
One of the members here Red pointed out a possible bug in the program concerning user names that have a space in them, thats what gives the "no mapping error" and thats why I suggested you manually change the permissions.
I haven't had the time to see if thats a bug in Ghost or Windows.