while surfing the net I found this cool blog about enabling backup and resoter for your group policies.
Jeremy Moskowitz wrote it and here’s a little preview of the article. On the end is the link to the complete article.
Continue reading “Enable Backup and Restore for Group Policy”
When System Center Data Protection Manager 2010 (DPM) is protecting Hyper-V guests using the Microsoft Software Shadow Copy provider (the VSS provider), DPM will be using software snapshots when backing up guests located on Cluster Shared Volume (CSV) disks. While the backup is in progress, the CSV will remain in re-directed access mode for the duration of the guest backup. This means all disk I/O for Guests located on that CSV will be in redirected mode and be going over the network instead of direct access to the CSV and performance may be affected. Continue reading “System Center Data Protection Manager 2010 Hyper-V protection: Configuring cluster networks for CSV redirected access”
By now you have probably Created a Central Store for Group Policy Administrative Templates and imported the Terminal Server & XenApp Tuning Group Policy, but what about backup? Did you know that Microsoft have created Group Policy Management Console (GPMC) scripting samples that makes it extremely fast and easy to backup Group Policy Objects (GPO). With these sample scripts you can backup all or single GPO’s, grant permissions, import, restore, list and more. Check out the script examples here.
Download and install the GPMC Scripting Samples and create a weekly scheduled task.
Command line example :
cscript "C:Program FilesMicrosoft Group PolicyGPMC Sample ScriptsBackupAllGPOs.wsf"
"%XA%Group PolicyBackups" /Comment:"GPO Weekly Backup on %DATE%_%TIME%"
If something should happen to your GPO it’s very easy to restore it, with a script or simply by selecting “Restore from Backup” within GPMC shown in the picture above.
If you ever are in the situation that your ePO 4.5 server crashed and you need to reinstall it check it this procedure for getting it started and running again:
NOTE: If you don’t follow these steps then you arein trouble. Make sure you have the same server name and same database instance name (EPOSERVER). Otherwise you can reinstall SQL again to get it working !!!!!