After performing an in-place upgrade on a Windows machine, you will find a WINDOWS.OLD folder in the root of C:. This folder will have a backup of your old program files, appdata and Windows folder… just in case you need to revert back or recover something that might have been lost during the upgrade. When you try to delete it though you are told you don’t have permissions. (more…)
Posts Tagged ‘permissions’
Tags: cleanup, delete, permissions, windows.old
Tags: groups, nesting, permissions
On a brand new System Center Orchestrator 2012 install the web console was showing the basic site, but would show no details for Runbooks or Runbook Servers.
It would work fine if I connected using the “Orchestrator Admin” account used during install, but other accounts were all having problems. It seemed obvious that permissions were the problem, but where exactly? All those same users could use the Orchestrator Designer console without any problem, so it seemed they had all the permissions needed.
Tags: permissions, web console
Have found an issue when using the Orchestrator Web Console where the permissions a user has are still active after they have been removed.
- Permissions are granted to an AD group to a runbook folder using the Designer console
- User is added to the AD group
- User can connect to Designer and also the Web Console to see and manage the runbooks in that folder
- Remove the user from the group
- In Designer, the user no longer has access and cannot see the folder or runbooks
- In the Web Console, the permissions are unchanged and the user can still view and manipulate the runbooks
Suggestions provided through a post to the technet forums suggested that the permissions are cached in the SQL database in the “Microsoft.SystemCenter.Orchestrator.Internal.AutorizationCache” table, however this table was already empty
Restarting the Servers, services, logging the user off and on etc made no difference. The permissions still persisted the following day.
Another user suggested this is a known bug and that they resolved it with a call to Microsoft. I can find no other mention/reference of this bug, so a call to Microsoft it is…