Install the support tools on windows 2003 server

Install the support tools on windows 2003 server

Support Tools (support tools) can be useful to see if there is a problem on your server. However, on Windows 2003 server, they are not installed by default.

To install, just go to this page for download: http://www.microsoft.com/download/en/details.aspx?id=7911.

Just run the file and follow the instructions for that after few clicks.

Then, just go to the directory C: \ Program Files \ Support Tools (command-line course).

Here is the list of tools:

- Acldiag.exe
- Addiag.exe
- Apmstat.exe
- Binddif.exe
- Bitsadmin.exe
- Browstat.exe
- Cabarc.exe
- Dcdiag.exe
- Depends.exe
- Devcon.exe
- Dfsutil.exe
- Dhcploc.exe
- Diruse.exe
- Dmdiag.exe
- Dnscmd.exe
- Dnslint.exe
- Dsacls.exe
- Dsastat.exe
- Dskprobe.exe
- Efsinfo.exe
- Exctrlst.exe
- Filever.exe
- Ftonline.exe
- Getsid.exe
- Gflags.exe
- Httpcfg.exe
- Iasparse.exe
- Ksetup.exe
- Ktpass.exe
- Ldp.exe
- Memsnap.exe
- Movetree.exe
- Msicuu.exe
- Msizap.exe
- Netcap.exe
- Netdiag.exe
- Netdom.exe
- Nltest.exe
- Ntfrsutl.exe
- Poolmon.exe
- Portqry.exe
- Remote.exe
- Repadmin.exe
- Replmon.exe
- Rsdiag.exe
- Rsdir.exe
- Sdcheck.exe
- Setspn.exe
- Shoaccs.exe
- Sidwalk.exe
- Spcheck.exe
- Windiff.exe
- Xcacls.exe

Read More

[facebook src="Uptodatewithme" width="500" height="400" hide-cover="true" posts="true"/]

Windows Server 2012 – Reasons For An Upgrade

Windows Server 2012 – Reasons For An Upgrade

Microsoft Windows Server 2012 provides the most current version of Microsoft Windows Server and is the successor to Microsoft Windows Server 2008 R2. Some clients may initially balk at Server 2012′s adoption of the new Microsoft windows 8 UI, but its new abilities regarding centralized control, virtualization, and storage space make the short-term pain worth enduring. Furthermore, Microsoft simple the platform’s certification to reduce customer confusion about which version can best provide their needs.

Server Manager 2012 features as the primary control program for Windows Server 2012. The new application allows clients to rely on one program for simultaneous analysis, control and management of multiple web servers. Administrators can handle features and perform other tasks to a single server or to server categories, and these categories can now consist of exclusive virtual servers. Furthermore, developments to remove management allow the provisioning of virtual servers without a Remote Desktop Protocol (RDP) connection. Other primary functionality developments consist of enhanced consoles for Server 2008 R2 tools such as VPN Reconnect, Direct Accessibility, and Branch Caching. Windows Server 2012 also boasts developments to flexibility and failover capacity for storage space clustering and File Share solutions, among many others.

Additionally, Windows 2012 provides new virtualization features along with private reasoning solutions. Hyper-V and System Center Virtual Machine Management (SCVMM) easily combine exclusive and actual solutions into one control User Interface. Users can access and handle in-house, reasoning, and hybrid exclusive systems at the same time, as well as make and move exclusive machines across reasoning systems from one SCVMM program. SCVMM also features live migration, allowing continued exclusive virtual servers to operate even while duplication and updating processes occur in the reasoning.

Hyper-V enhances disaster recovery with Hyper-V Imitation – a cost-effective alternative to logging all changes from a primary server to a duplicate server. The function uses compression to conserve data transfer usage and features with standalone hosts as well as any combination of clusters.

As for storage space options, Server 2012 developments scalability, security, and reliability with the new Storage Spaces function. This option allows the user to use hard disks to make a storage space pool and partition them in a manner similar to actual disks.

Microsoft clients frequently find themselves with too many unclear choices about which version will best provide them for the best price. To remedy this, Microsoft provides Windows Server 2012 in only four editions: Base, Requirements, Conventional, andDatacenter. Base and Requirements provide relatively low-cost per-server licenses to those with minimal or small-scale needs. The Conventional and Datacenter versions provide more application with certification in accordance with the number of processors and on Client Accessibility Licensing (CAL).

Windows Server 2012 assumes the new tile-based Microsoft Windows 8 interface, but the uninitiated should appreciate the new platform’s centralization and virtualization features long after climbing the minor learning curve. With Windows simple certification program, clients should have little difficulty finding and pricing their optimal solution.

Read More

[facebook src="Uptodatewithme" width="500" height="400" hide-cover="true" posts="true"/]

Step-By-Step: Active Directory Migration from Windows Server 2003 to Windows Server 2012 R2

Step-By-Step: Active Directory Migration from Windows Server 2003 to Windows Server 2012 R2

With the end of support for Windows XP, Office 2003 and Exchange 2003 now upon us, April 8th 2014 to be exact, attention now turns to Windows Server or specifically Windows Server 2003.  End of support for Windows Server 2003 is currently slated for July 14th 2015 and a great many organizations still utilize said offering as the cornerstone to their infrastructure to this day.  One question to keep in mind though is that with the move on the client end to Windows 8.1, will Windows Server 2003 or 2003 R2 be robust enough to properly enable employees and provide secure access to the plethora of devices in a world now dominated by BYOD?  Alternatively an IT administrator might ponder on the further enablement invoked via the deployment of Windows Server 2012 R2 should it be deployed in said organization.  Lets explore this possibility via the cornerstone of access enablement offered via Windows Server by investigating the evolution of the Active Directory offering now found in Windows Server 2012 R2

As you may know, Active Directory provides authentication and authorization mechanisms as well as framework from within other related services that can be deployed. As an LDAP compliant database, it commonly contains the most used objects such as users, computers, and groups organized into organizational units or OUs by any number of logical or business needs. Group Policy Objects or GPOs are then linked to OUs to centralize the settings for various users or computers across an organization. Part of the quandaries that IT professionals face is taking advantage of nuances provided in Active Directory in newer server offerings such as Windows Server 2012.  As detailed in Pierre's post, "Windows Server 2012 Active Directory – What’s New?", Active Directory provided in Windows Server 2012 R2 is provided impactful enhancements.  Yet some organizations choose not to migrate due to reasons of uncertainty.

This Step-By-Step has been created to assist with that uncertainty and provide guidance for IT professionals looking to migrate their organizations Active Directory offering from Windows Server 2003 to 2012 R2.

Prerequisites

1. Download Windows Server 2012 R2 and create your lab environment. (Instructions can be found here)
2. Complete Step-By-Step: Adding a Windows Server 2012 R2 Domain Controller to an Existing Windows Server 2003 network

Transferring the Flexible Single Master Operations (FSMO) Role

1. Open the Active Directory Users and Computers console on your new Windows Server 2012 R2 computer.
2. Right click your domain and select Operations Masters in the sub menu.
3. In the Operations Masters window, ensure the RID tab is selected.
4. Select the Change button.
   
   
5. Select Yes when asked about transferring the operations master role.
6. Once the operations master role has successfully transferred, click OK to continue.
7. Ensure the Operations Master box now shows your new 2012 R2 Windows Server.
8. Repeat steps 4 to 6 for the PDC and Infrastructure tabs.
9. Once completed, click Close to close the Operations Masters window.
10. Close the Active Directory Users and Computers window.

Changing the Active Directory Domain Controller 

1. Open the Active Directory Domains and Trusts console on your new Windows Server 2012 R2 computer.
2. Right click your domain and select Change Active Directory Domain Controller... in the sub menu.
3. In the Change Directory Server window, select This Domain Controller or AD LDS instance.
4. Select your new 2012 R2 Windows Server.
   
   
5. Click OK to continue.
6. Back in the Active Directory Domains and Trusts window, hover over the Active Directory Domains and Trusts found in the folder tree on the left hand side to ensure the server now reflects your new 2012 R2 Windows server.
7. Right click Active Directory Domains and Trusts found in the folder tree and select Operations Manager... in the sub menu.
8. In the Operations Master window, click Change to transfer the domain naming master role to the 2012 R2 Windows Server.
9. When asked if you are sure you wish to transfer the operations master role to a different computer, clickYes.
10. Once the operations master is successfully transferred, click OK to continue.
11. Click Close to close the Operations Master window.
12. Close the Active Directory Domains and Trusts console.

Changing the Schema Master

1. Open a command prompt in administration view on your new Windows Server 2012 R2 computer.
2. On the command prompt window, enter regsvr32 schmmgmt.dll and hit enter.
3. Once completed successfully, click OK to close the RegSvr32 window.
   
   
4. Close the command prompt.

Add the Active Directory Schema Console from MMC

1. Open a MMC console on your new Windows Server 2012 R2 computer.
2. Click File > Add/Remove Snap-in...
3. In the Add or Remove Snap-ins window, select Active Directory Schema and click the Add > button.
   
   
4. Click OK to continue.

Change the Schema Master

1. In the same MMC console, right click Active Directory Schema and select Change Active Directory Domain Controller... in the sub menu.
2. In the Change Directory Server window, select This Domain Controller or AD LDS instance.
3. Select your new 2012 R2 Windows Server.
4. Click OK to continue.
5. A warning will appear stating that the Active Directory Schema snap-in in not connected. Click OK to continue.
6. Hover over the Active Directory Schema folder in the folder tree to ensure the new Windows Server 2012 R2 computer is shown. 
7. Now right click Active Directory Schema and select Operations Master... in the sub menu.
8. In the Change Schema Master window, click Change to transfer the schema master role to the 2012 R2 Windows Server. 
9. When asked if you are sure you wish to transfer the schema master role to a different computer, click Yes.
10. Once the schema master is successfully transferred, click OK to continue.
11. Click Close to close the Change Schema Master window.
12. In the MMC, click File > Exit.
13. When asked to save the console, click No.

 Once completed, open the Active Directory Users and Computers console to verify that the Active Directory database successfully replicated to your new Windows Server 2012 R2 computer.  Be aware that the database replication may take some time depending on the number of objects in Active Directory.

Removing the 2003 Windows Server from the Global Catalog Server

1. Open Active Directory Sites and Services on your new Windows Server 2012 R2 computer.
2. Expand the Sites folder, then the Default-First-Site-Name folder, then the Servers folder.
3. Expand both listed servers. One should be your new 2012 Windows Server and one should be you 2003 Windows Server.
4. Right click NTDS Settings found under your old 2003 Windows Server.
5. In the sub menu, select Properties.
6. Under the General Tab, unselect Global Catalog and then click the Apply button.
7. Click OK to continue.
8. Close the Active Directory Sites and Services window.
9. Verify that your new 2012 R2 Windows Server is running the FSMO role by opening the command prompt in Administrative view and running the following command: Netdom query fsmo.
10. In the Network and Sharing Center, be sure to change the Preferred DNS server to match the Alternate DNS server, then delete the IP address listed under the Alternate DNS server should it currently be pointed to the old 2003 Windows Server.

All that's left is to demote the old 2003 Windows server by first adding the new 2012 R2 Windows Server as the Primary DNS, followed by running DCPROMO to demote the old 2003 Windows server. Be sure to also visit Microsoft Virtual Academy created to further enable IT professionals in regards task such as migrating to Windows Server 2012 R2.

Read More

[facebook src="Uptodatewithme" width="500" height="400" hide-cover="true" posts="true"/]

Step-By-Step: Migrating a Windows Server 2003 file server, NTFS and Share Rights to Windows Server 2012 R2

Step-By-Step: Migrating a Windows Server 2003 file server, NTFS and Share Rights to Windows Server 2012 R2

With time ticking in regards to end of support on Windows Server 2003, most IT professionals are in the midst of planning their migration. While most are focusing on migrating Active Directory and DHCP, some have expressed interest in migrating file services as well. Windows Server 2012 R2 provides a robust solution in terms of file services for organizations to take advantage of. Hence the creation of this Step-By-Step to further assist the process.

Step 1: Prepping the new Windows Server 2012 R2 machine

1. Via Server Manager, navigate to Manage > Add Roles and Features
    
2. Click Next until the Select Features screen is visible
    
3. Ensure PowerShell 4.0 and ISE are installed
    
4. Select Windows Server Migration Tools and click Next
   
   
   
   Note: The Windows Server Migration Tools include additional cmdlets that assist in the migration of server roles, OS settings files and shares from legacy Windows Servers
    
5. Click Install
   Note: A reboot of this server might be required

Step 2: Generating the necessary PowerShell files for Windows Server 2003

1. On the Windows Server 2012 R2 machine, open PowerShell in Administrator mode and type the following:
   
   SmigDeploy.exe /package /architecture X86 /os WS03 /path <deployment folder path>
   
   Note: Insert your desired path replacing deployment folder path in the script above
    
2. Create the C:\MigratingTools folder on the Windows Server 2003 machine
    
3. Copy the content from Windows Server 2012 R2 folder <deployment folder path> to the Windows Server folder C:\MigratingTools\
    
4. On the Windows Server 2003 machine in the C:\MigratingTools folder, runSMIGDEPLOY.EXE
    
5. On the Windows Server 2003 machine in the C:\MigratingTools\SMT_ws03_x86\ folder, click & run ServerMigration.pcs1

Step 3: Completing the migration

1. On the Windows Server 2012 R2 machine, still running PowerShell in Administrator mode and type the following:
    Add-PSSnapin Microsoft.Windows.ServerManager.MigrationGet-Command -Module Microsoft.Windows.ServerManager.MigrationReceive-SmigServerData
    
2. Enter a desired migration password when prompted
    
3. On the Windows Server 2003 machine, open PowerShell in Administrator mode and type the following:
    Send-SmigServerData -ComputerName "Computer Name" -DestinationPath "X:\Users" -Include All -SourcePath "F:\users" -Recurse
   
   Note: Insert your Windows Server 2012 R2’s name replacing Computer Name in the script above
    
4. On the Windows Server 2003 machine, open the registry editor and navigate to HKEY_LOCAL_MACHINE>SYSTEM>CurrentControlSet>Services>LanmanServer>Shares
    
5. Right-click on the Share Key and select Export
    
6. Save the exported key to a folder accessible by the Windows Server 2012 R2 machine
    
7. On the Windows Server 2012 R2 machine, right-click the saved registry file exported from the Windows Server 2003 machine and select Merge
    
8. Restart the Windows Server 2012 R2 machine
   
   Note: If your new server uses different drive allocations than the Windows 2003 Server, run the registry editor on the Windows Server 2012 R2 machine > navigate to HKEY_LOCAL_MACHINE>SYSTEM>CurrentControlSet>Services>LanmanServer>Shares and click on the share in question. Edit the Multi-String Path value to refect the new drive allocation

Read More

[facebook src="Uptodatewithme" width="500" height="400" hide-cover="true" posts="true"/]