After installing Service Pack 1 for Data Protection Manager 2007 and upgrading each of the agents on my servers, most of my protected servers would fail to back up with one of the following errors:
Only a hand full of jobs completed successfully. Consistency checks would fail also.
In an earlier post a script was published which automatically sends users a warning message/mail when their password is about to expire.
A more simple approach would be to scan the AD for disabled and locked accounts manually or at a set interval, say each morning.
When using Data Protection Manager to back-up the system state of your servers you will find that a folder with the name DPM_SYSTEM_STATE is created on your C:\ drive on the protected server. When disk space is insufficient to support this additional data, you can alter the location where this data is stored:
During the installation of MOSS 2007 I quite often encounter the following error message in the Windows Event Viewer:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with
CLSID {61738644-F196-11D0-9953-00C04FD919C1}
to the user <serverName>\mossService SID (S-1-5-21-<serviceSID>). This security permission can be modified using the Component Services administrative tool.
After searching the web and testing i found that the permissions on the DCOM+ Component Service, specifically the IIS WAMREG Admin Service, to be wrong.
As a part-time systems administrator for hire, I also install, configure and administer Exchange 2007 environments. One of the more complex matters is explaining in layman’s words the architecture of an Exchange 2007 environment. To add to the complexity, Microsoft has released a map/poster that illustrates and explains the different facets: