Thursday, July 2, 2015

Migration is worth it !!! Windows Server 2003 Support is ending July 14, 2015

Here’s footsteps for you to migrate it to 2012 server-:

Setting plot.

1.       Initially install windows server 2012 R2.
2.       Complete step by step: add a window server 2012 R2 domain controller to an existing windows server 2003 network.

Transferring the flexible single master operations (FSMOS).

1.       Start this process by opening the Active directory users and computers built on your new windows server 2012 R2 computer.
2.       Now, just right click your domain and select Operations masters given in sub-menu.
3.       Then in Operation masters windows, ensure the RID tab is selected.
4.       At right side, look for change option and select it.
5.       Now you will asked about transferring the operation master role, select yes for it.
6.       Click on OK to continue, after the operations master role has successfully transferred.
7.       Now guarantee the operations master box and your new 2012 R2 window server.
8.       Take over steps 4 to 6 for the infrastructure tabs and PDC.
9.       After completion, just click Close to close the Operation masters window.
10.   Now close the Active directory users and computers windows.


Changing the active directory domain controller.

1.       Again, open the Active directory users and computer built on your new windows server 2012 R2 computer.
2.       By right clicking on your domain select Operations masters given in sub-menu.
3.       Select the Domain controller or AD LDS instance from Change directory server window.
4.       Here’s your new 2012 R2 windows server, just select it.
5.       To continue click OK.
6.       Comeback to the Active directory domain and trusts window to look over the active directory domain and trusts found in the folder tree on left hand side to assure the server so to reflect your new 2012 R2 windows server.
7.       Now by right clicking active directory domain and trusts found in the folder tree select Operation manager in sub menu.
8.       Click Change to transfer the domain naming master role to 2012 R2 windows server in Operation master window.
9.       Click yes if you like to transfer the operations master role to different computer, when asked.
10.   Click ok to continue after the operations master is successfully transferred.
11.   Now click the Operation master window.
12.   Also close the Active directory and trusts console.


Changing the Schema master.

1.       Go for opening a command prompt in administration view on your new windows server 2012 R2 computer.
2.       Type regsvr32 schmmgmt.dill ,hit enter on the command prompt window.
3.       Now click Ok to close the Regsvr32 window.
4.       Just close the command prompt now.

Add the active directory schema console from MMC.

1.        In new window server 2012 R2 computer a MMC console.
2.       Click File>Add/Remove snap in
3.       Then select Active directory schema and click the Add>button in Add or Remove snap-ins window.
4.       Click Ok to continue.

Change the schema master.

1.        Just in the same MMC, select Change Active directory domain controller by right clicking active directory schema.
2.       Now select This domain controller or AD LDS instance in the change directory server.
3.       Select your new 2012 R2 windows server.
4.       To continue click ok.
5.       Now a warning will be seen stating you that the active directory schema snap-in not connected. Ok to continue.
6.       Look for the Active directory schema folder in folder tree to ensure the new window server 2012 R2 computer is shown.
7.       Do right click on Active directory schema folder in folder tree to ensure the new window server 2012 R2 computer is shown.
8.       In change schema master window, click change for transferring the schema master role to 2012 R2 window server.
9.       Click yes if you are sure to transfer schema master role to different computer.
10.   Click Ok after schema master is successfully transferred.
11.   Now close the Change schema master window.
12.   In the MMC, click File>Exit.
13.   Click no, when ask to save console.

After completion just open the active directory users and computer console to verify that the active directory database successfully replicated to your new windows server 2012 r2 computer. take care of data base replication as it may take some time depending on number of objects in active directory.


 Removing the 2003 windows server from the global catalog server.

1.       Now just open Active directory sites and services on your new windows server 2012 R2 computer.
2.       Now expand site folder, then the default-first-site-name folder, then the server’s folder.
3.       Expand both listed server.one should be your new 2012 windows server and other should be 2003 window server.
4.       Now right click NTDS settings found under your old 2003 windows server.
5.       Select properties in sub-menu.
6.       Under general tab, after unselecting global catalog. Just click the apply button.
7.       Click ok to continue.
8.       Now close the Active directory sites and services windows.
9.       Prefer to verify that your new 2012 R2 window server is running the FSMO role by opening the command prompt in administrative view and running given command :Netdomquery Fsmo.

10.   Now in Network and sharing centre, do not forget to change the preferred DNS server to match alternate DNS sever, then delete the IP address listed under the alternate DNS server. It currently be pointed to old 2003 window server.  

Thursday, August 21, 2014

Windows Server 2003 Support is Ending July 14, 2015

Do You Know : -

Windows Server 2003 Support is Ending July 14, 2015, so prepare yourself to change the Server OS.



Thursday, July 4, 2013

Google Chrome didn't shut down correctly. To reopen the pages you had open, click Restore. (Fixed)

I have tried many ways to remove this error "Google Chrome didn't shut down correctly. To reopen the pages you had open, click Restore" which is showing in Google search result. but not able to fixed the same.

then i have tried my way to rid out of this error. below is the simple solution for the same:

1. Uninstall Google Chrome.
2. Restart the computer.
3. Then go to C:\Users\user_name\AppData\Local then delete the Google folder which includes Chrome & Crash report folders.
4. Install Google Chrome Again.

and Guess What ?  Google chrome will run perfectly.


www.makemyserver.com