Backup & Restore System State Backup on Windows2008 Domain Controllers

Backup & Restore System State Backup on Windows2008 Domain Controllers

On Windows Server 2008 R2, there are approximately 50,000 system state files, which use approximately 4 GB of disk space in the default installation of an x64-based computer. The fastest and easiest way to back up and restore a server’s system state is to use Wbadmin. 

With Wbadmin, you can use:

START SYSTEMSTATEBACKUP command to create a backup of the system state for a computer and  START SYSTEMSTATERECOVERY command to restore a computer’s system state. 

(Note that when you select a system state restore on a domain controller, you have to be in the Directory Services Restore mode.) To back up a server’s system state, type the following at an elevated command prompt:

wbadmin start systemstatebackup -backupTarget:VolumeName
Here VolumeName is the storage location for the backup, such as F:.

To restore a server’s system state, type the following at an elevated command prompt:
wbadmin start systemstaterecovery -backupTarget:VolumeName
Here VolumeName is the storage location that contains the backup you want to recover, such as F:.

Additionally, you can do the following:

• Use the –recoveryTarget parameter to restore to an alternate location.
• Use the –machine parameter to specify the name of the computer to recover if the original backup location contains backups for multiple computers.
• Use the –authSysvol parameter to perform an authoritative restore of the SYSVOL.

You can also recover the system state by using a backup that includes the system state or by performing a recovery.

Fine Grained Password Policies in Windows 2008 R2

Fine Grained Password Policies in Windows 2008 R2

To setup the fine grained password policies in R2 can be setup in 2 ways either by adsiedit.msc tool OR ldp.exe tool.

Thanks to CEYHUN who shared the below video:

Else you can follow the below URL :

Steps to create the Fine grained password policies in below link:

http://blogs.technet.com/b/seanearp/archive/2007/10/06/windows-server-2008-fine-grained-password-policy-walkthrough.aspx

But I preferred tool to create Fine grained password policies is adsiedit.msc

Outlook Starting Issues

Outlook starting Issues:

http://support.microsoft.com/kb/272227 - Link for troubleshoot Outlook Issues

To troubleshoot the outlook which is not starting then run this command in CMD;

outlook.exe /resetnavpane


To repair the PST file run SCANPST.exe

C:\Program Files\Microsoft Office\Office14 - File path of Scanpst.exe PST repair tool

http://www.outlook-tips.net/beginner-user/start-outlook-in-safe-mode/

How to import Catalogs into a Backup Exec 12.x or later for Windows Servers installation

http://www.symantec.com/business/support/index?page=content&id=TECH68896 - link

Problem

How to import Catalogs into a Backup Exec 12.x or later for Windows Servers installation

Solution

To import catalog files to a new or upgraded installation of Backup Exec (tm) 12.x or later from a server running the same or a prior version of Backup Exec, perform the following steps:

1. Locate the catalogs folder where the catalogs will be imported from.

2. Copy all the files from catalogs folder and subfolder (if one exists) with extensions .xml, and .fh, as shown (Figure 1)

3. Paste the copied files to the root of current (target) catalogs folder.

Note: By default the catalogs are stored at the following location:

  C:\Program Files\Symantec\Backup Exec\Catalogs.

4. Once all the files are moved into the new catalogs folder, restart Backup Exec services to re-index the imported catalogs.  Depending on the amount of catalogs imported, it may take some time for this to complete.  Check the Restore Selection view to confirm the catalogs have imported correctly.  If the catalogs indexed properly, the files will be moved to a server named subfolder under the catalogs folder and a file named UpgradeIndexInfo.upg will also be present (Figure 2)

Note:  Even though the Restore Selections reflecting the catalogs migrated from another media server may now show, a restore operation can only be performed after an inventory of the respective media has been performed. When catalogs are copied to a media server that has not used or inventoried the media in question, the media information is not present in the Backup Exec Advanced Device And Media Management (ADAMM) database, and the restore job will fail do to it referencing a media ID that is unknown.

Note:  If the Restore Selections do not show properly after performing the steps above, perform the steps in the following Technote to re-index the catalogs from a command prompt:


Errors occur after upgrading Backup Exec and selections are missing in the Restore Selections window
  http://www.symantec.com/docs/TECH67271

Import one PST into all the mailboxes located in Exchange2010 in one-short

Issue : Import one PST into all the mailboxes in the Exchange Organization what I did was;

Resolution:
I have exported all the mailboxes alias names to .CSV file & run below command to Import the PST into the
mailbox aliases

Import-CSV \\mbx\PST\New.csv | Foreach{ New-MailboxImportRequest -Mailbox $_.Alias -FilePath \\mbx\PST\v2cal.pst}

After I ran above command, it was giving below error;
Cause : I was not added the user account which I was logged on Exchange cas server into the share where I had kept PST file, we need to give Full access to the share for that account.

Import-CSV \\mbx\PST\New.csv | Foreach{ New-MailboxImportRequest -Mailbox $_.Alias -FilePath \\mbx\PST\v2cal.pst}
Import-Csv : Cannot open file "\\mbx\PST\New.csv".
At line:1 char:11
+ Import-CSV <<<<  \\mbx\PST\New.csv | Foreach{ New-MailboxImportRequest -Mailbox $_.Alias -FilePath \\mbx\PST\v2cal.ps
t}
    + CategoryInfo          : OpenError: (:) [Import-Csv], UnauthorizedAccessException
    + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.ImportCsvCommand

After changed the above settings, it's working fine.

In one-short am able to import one PST into all the mailboxes in my ORG.

User account which I am using its not added into the share where I had kept the PST file.

http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/c3ad4e47-1156-4ea6-b846-ec67815e0572 - link

Copying Files Over Remote Desktop

Hi All,

We can copy the files from local machine to Remote Desktop machine by using the below link;

Thanks to the people those who explore new tips ;

http://haacked.com/archive/2010/05/17/remote-desktop-file-copy.aspx

SYSVol content is not replicating from one DC to another DC

SYSVol Content is not replicating from one DC to another DC:

Event Error log is:

Resolution is:To perform a nonauthoritative restore, stop the FRS service, configure the BurFlags registry key, and then restart the FRS service. To do so:
1. Click Start, and then click Run.
2. In the Open box, type cmd and then press ENTER.
3. In the Command box, type net stop ntfrs.
4. Click Start, and then click Run.
5. In the Open box, type regedit and then press ENTER.
6. Locate the following subkey in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\NtFrs\Parameters\Backup/Restore\Process at Startup
7. In the right pane, double-click BurFlags.
8. In the Edit DWORD Value dialog box, type D2 and then click OK.
9. Quit Registry Editor, and then switch to the Command box.
10. In the Command box, type net start ntfrs.
11. Quit the Command box.

When the FRS service restarts, the following actions occur:
• The value for BurFlags registry key returns to 0.
• Files in the reinitialized FRS folders are moved to a Pre-existing folder.
• The FRS database is rebuilt.
• The member performs an initial join of the replica set from an upstream partner or from the computer that is specified in the Replica Set Parent registry key if a parent has been specified for SYSVOL replica sets.
• The reinitialized computer performs a full replication of the affected replica sets when the relevant replication schedule begins.