SYSVOL folder not replicating on Backup domain controller

Replication issue between two domain Controller windows server 2003 :

SYMPTOMS:-

1. SYSVOL  folder not replicating on Backup domain controller.

2. or SYSVOL folder accidently deleted from domain controller.

WORKAROUND :

1.Stop the FRSservice on backup domain controller with below command:

 Net stop ntfrs

2. locat below registry Set DWORD value to D2 :

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Paramaters\Backup/Restore\Process at Startup

Double-click the BurFlags Value Name, a REG_DWORD data type, and set the data value to D4, using the Hex radix.

• Exit the Registry Editor.

3. login to PDC server and stop the FRS service with below command

Net stop ntfrs

4. Navigate below registry:

•HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Paramaters\Backup/Restore\Process at Startup.

• Double-click the BurFlags Value Name, a REG_DWORD data type, and set the data value to D4, using the Hex radix.

• Exit the Registry Editor.

5. start the FRS service : with below command

Net start ntfrs

6. wait for some time, then login to backup domain controller.

7. start frs service on BDC with below command:

Net start ntfrs

wait for some time, then restart the netlogon service on both server.

check event log for below event on both server.

Below event trigger after starting FRS service on the both server.

The File Replication Service successfully added the connections shown below

to the replica set on promary domain controller:

 "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"

After completing process, an event 13516 is logged to signal that FRS is operational on both server.

Too Many MAPI Connections

The Microsoft® Exchange Server Analyzer Tool reads the following registry entry to determine if the default maximum number of folders that can be opened per MAPI session has been changed: 

Outlook client doesn’t update folders automatically. On the status bar instead of “All folders are up to date” message “This folder was last updated on …” is displayed. 
and hence Exchange server logs the following error: 

Event ID: 9646 
Type: Error 
Source: MSExchangeIS 
Description: 
Mapi session "/o=First Organization/ou=Administrative Group/cn=Recipients/cn=dmock" 
exceeded the maximum of 500 objects of type "objtFolder". 

The number of server-side objects that are allowed by clients is limited to prevent a single client from the exhausting resources on the Exchange server. 

To resolve this problem: we need to modify registry value below are steps. 

1. Open Registry Editor and navigate to: 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchangeIS 
2. Right click ParametersSystem and create New -> Key 
3. Enter MaxObjsPerMapiSession and confirm creation of the new sub-key 
4. Right click newly created key, create new DWORD value called objtFolder and give it a decimal value bigger than default 500. 
5. Create another DWORD value called objtFolderView and give it the same value.

Note : Take Registry backup before modifying any registry entry.

Blackberry server need reboot after rebooting Exchange server

Couse :-
After rebooting exchange server,  BlackBerry users emails are not coming through. Even though emails they send from their BlackBerrys seem to send fine, the recipients are not receiving them either. 

Restart the BlackBerry Enterprise Services (BES) server or individual services.  problem of Blackberries not being able to send/receive emails after an Exchange server reboot unless the BES server is also rebooted or the Blackberry services are restarted.

NOTES: - What happens in the background is that BES loses MAPI connections to the Exchange server and is not able to re-establish this once the Exchange services come back online. Exchange service restarts can happen for any reason, Windows update, someone manually restarting the server. 
 Script can be created on this,  if exchange server rebooted , BES services will restart automatically restart within  5 to 10 min after rebooting exchange server.    

Please let us know if you are facing any other issues.


More information please refer below link :- 
http://blog.mohsinabbas.com/2011/02/16/bes-services-to-restart-automatically-after-exchange-reboot/
http://www.virtuallyimpossible.co.uk/blackberry-users-cannot-send-or-receive-emails-after-exchange-reboot/
http://www.blackberryforums.com/bes-admin-corner/102832-some-users-unable-send-due-invalid-addresses.html

How to Delete a User Profile from Server 2008 Terminal Server

1.	Identify the SID of the user whose profile needs to be deleted. - I typically use ADSI Edit on a domain controller to do this. Open ADSI Edit, navigate through the OU’s until you find the user, CN=”Username”, right-click and choose properties. Scroll to the object property labeled “objectSid”. Document that SID because you will need it shortly.
2.	Verify that the user is not logged into the server. - From a command prompt type “query user” and verify that the user is not listed.
3.	Open the folder directory where the server user profiles are stored. - Server 2008 default is “C:\%USERNAME”.
4.	Delete the profile folder for the user.
5.	Open the registry editor. - Start > regedit
6.	Navigate to the following: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
7.	Locate the sub-key that is named the same as the documented SID from earlier. Right-click on the sub-key choose delete.
8.	Have the user log back in. If the user reports no problems then you have successfully deleted a user profile. - If the user logs in and is presented with a pop-up from the system try stating that the user is being logged in with a temporary profile then proceed to step 9.
9.	If the user gets logged in with a temporary profile then have them log out, open up the registry editor once again, and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList.
10.	Look for a sub-key named the same as the documented SID followed by a “.bak”. Right-click on that sub-key and choose delete.
11.	Have the user attempt to login. The user should no longer be prompted by the temporary profile pop-up.

Referral  URL

http://community.spiceworks.com/how_to/show/1595

http://www.geekyway.com/deleting-local-user-profile-terminal-server-2008/

Copy the users’ shared folders to the Destination Server by using RoboCopy

To copy users’ shared folders

1.   On the Destination Server, click Start, right-click PowerShell, and then click Run as administrator. 2.   On the User Account Control page, click Continue. 3.   At the command prompt, type the following: Robocopy \\<SourceServerName>\Users \\<DestinationServerName>\UserShares /E /COPY:DATSOU /R:10 /LOG:C:\Copyresults.txt.

Copy additional shared folders to the Destination Server

To copy folders to the Destination Server:-

1.   On the Destination Server, click Start, right-click  PowerShell, and then click Run as administrator. 2.   On the User Account Control page, click Continue. 3.   At the command prompt, type the following: robocopy \\<SourceServerName>\<ShareName> <disk>:\<FolderName> /E /R:10 /COPY:DATSOU /LOG:C:\Copyresults.txt, where <disk>:\<FolderName>  is the physical location that you want to copy to your Destination Server. 4.   Repeat step 3 for additional folders that you want to copy to the Destination Server.

Manually Synchronize time with external NTP Server:

Follow below instructions :-

First, locate your PDC

1.  Server. Open the command prompt and type: C:\>netdom /query fsmo
2. Log in to your PDC Server and open the command prompt.
3. Stop the W32Time service: C:\>net stop w32time
4. Configure the external time sources, type: C:\> w32tm /config /syncfromflags:manual /manualpeerlist: “0.ntp.pool.org, 1.ntp.pool.org, 2.ntp.pool.org”
5. Make your PDC a reliable time source for the clients. Type: C:\>w32tm /config /reliable:yes
6. Start the w32time service: C:\>net start w32time
7. The windows time service should begin synchronizing the time. You can check the external NTP servers in the time configuration by typing: C:\>w32tm /query /configuration
8. Check the Event Viewer for any errors.

 ----------------------------------------------------------------------------------------------------

w32tm /config /manualpeerlist:0.pool.ntp.org /syncfromflags:manual /reliable:yes /update

If you enter a command:

1. w32tm /unregister

and get error 0x80070002, it says that failed to stop the service.
Enter
2. Net stop w32time
to stop it. After stopping, it will automatically be removed.
Issuing commands you create the service again with all the default values:

3. w32tm /register    (this command create service and reset all setting)

4. Net start w32time  (this command start time service)