Disk Management and Explorer Show Different Drive Size

 I ran into this issue today when trying to extend out the drive size on a data drive on our primary file server.  After expanding the virtual disk in VMware, I brought up computer management (compmgmt.exe if you want to go command line quicker).

I expanded out the disk and immediately noticed that explorer didn't reflect that change after a refresh.  Also, disk management could no longer access the disk to make any edits.  I restarted the virtual disk service with no success.  A restart also proved futile.

MAKE A BACKUP BEFORE RUNNING THESE COMMANDS!

After some quick research, here is the fix.  Use DISKPART from an elevated command prompt.  Just follow the commands below and choose the proper disk on your VM.  After running the command, a quick refresh of explorer now shows the correct size.

Good luck!

Unable to scan IIS status - The IIS Common Files... Server 2012/2012 R2

I ran into this issue today while trying to run the Microsoft BPA (Best Practices Analyzer) 2.3 on a Windows Server 2012 R2 box with IIS 8.5 installed.  Below is the full text of the error:

"Unable to scan IIS status - The IIS Common Files are not installed on the local computer.  Refer to the system requirements list under the Microsoft Business Security Analyzer Help."

Here's the short fix:

Go back into Roles and under Web Server (IIS) and install IIS 6 Management Compatibility --> IIS 6 Metabase Compatibility.

Apparently from what I find this is a Windows Server 2003 item that hasn't been updated in the current server platform documentation on the MBSA to reflect the need for this additional set of files.

The longer explanation is that in order for the MBSA to be able to scan IIS properly it needs to have IIS 6 Management Compatibility turned on and more specifically the IIS 6 Metabase Compatibility.

I hope this one helps as it took me quite a bit of research to run this issue down.

Good luck.

Exchange 2013 Installation Step-by-Step Cheat Sheet

Ok so I've setup a new Exchange 2013 server for a customer and got it installed with no errors.  These instructions pertain to installation on Windows Server 2012/2012R2.

I have condensed it down to make sense.  We all know TechNet instructions look like they were written by a lawyer.

I hope this helps with your install.  Good luck.

1. Install all OS updates

2. Install all the following prereqs

- .NET Framework (already on Server 2012R2).  Just use the server manager to install this as a Feature.

- Remote Tools Admin Pack ( Install-WindowsFeature RSAT-ADDS )

- Windows Components ( Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation )

- Install Microsoft Unified Communications Managed API 4.0, Core Runtime 64-Bit

3. Extend the AD schema.  Use Command Prompt to drive letter with Exchange ( setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms ).  When setup completes allow some time for AD replication to complete across all DCs.

4. Prepare AD for Exchange.  Use Command Prompt to drive letter with Exchange ( Setup.exe /PrepareAD /OrganizationName:"" /IAcceptExchangeServerLicenseTerms )

5.  Prepare all domains for Exchange 2013.  Use Command Prompt to drive letter with Exchange ( Setup.exe /PrepareAllDomains /IAcceptExchangeServerLicenseTerms )

6.  Install Office 2010 Filter Packs - Version 2.0  http://go.microsoft.com/fwlink/?LinkID=191548 

7.  Install Office 2010 Filter Packs - Version 2.0 SP1  http://go.microsoft.com/fwlink/?LinkID=262358 

8. Run setup.exe.  Follow prompts and allow wizard to complete install.

That's pretty much all there is to it to get it installed. 

If you want more information on detailed installation, configuration after install, and maintaining then I highly recommend you read Mastering Microsoft Exchange Server 2013.  I did and it has been a tremendous reference point for me now that Exchange 2013 deployments are becoming more common for me.

Enjoy the read and good luck!

Windows XP can't access Server 2012 File Cluster

I ran into this one today and it took me all morning to finally find a fix for it.  It appears this is a known issue with Microsoft and even though they have a supposed "hot-fix" for it you can install on the 2012 file servers that doesn't fix it.

There is however a work around that immediately fixed the problem for me once I found it out about it.

The text of the error follows:

You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

Logon Failure: The target account name is incorrect.

I also noted in the event log on the client a kerberos event failure every time the share was attempted to be accessed.

Event Type: Error Event Source: Kerberos

Event Category: None

Event ID: 4

Date: 14/05/2013

Time: 08:27:30

User: N/A

Computer: XPClient

Description:

The kerberos client received a KRB_AP_ERR_MODIFIED error from the server fileservernode$. The target name used was cifs/Server.domain.int. This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named machine accounts in the target realm (Domain.INT), and the client realm. Please contact your system administrator.

Open Failover Cluster Manager

Go to Roles - Resources Tab - File Server

Right Click the File Server role - Take Offline

Wait for it to go offline, then Right Click - More Actions - Repair

Wait for it to come back online

This seems to take care of the problem....also while you're at it upgrade from XP.  :)

Server 2012 Event ID 13555

I ran into this one today.  It involved two brand new 2012 servers that had only been in service since December of 2012.  The error appears to have started on 4/27/2013 and didn't present itself as an issue (since there's no IT staff there to review server logs) until new workstations were being put in and group policy was not applying to some of them.

The event log gave error 1355.  In order to fix it you need to do a non-authoritative restore of the SYSVOL folder.  Just make a simple backup of it just in case from another good domain controller.  Follow the steps below and for me it fixed it right away.  There's no need to restart the server and I noticed the replication began and ran properly right away.

Here's the exact fix:

To back up and restore the SYSVOL data, follow these steps:

1. Back up the following folders in a temporary location that is not in the SYSVOL folder:
   • %SystemRoot%\SYSVOL\Domain\Policies
   • %SystemRoot%\SYSVOL\Domain\Scripts
   Note To retain the permissions for these folders, back up these folders in a location that is on the same volume as the SYSVOL folder.
2. Perform a non-authoritative restore on this replica set. To do this, follow these steps:
   1. Click Start, click Run, type cmd, and then click OK.
   2. At the command prompt, type the following command, and then press ENTER:
      net stop ntfrs
   3. Click Start, click Run, type regedit, and then click OK.
   4. Locate and then click the following registry subkey:
      HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
   5. Right-click the
      BurFlags
      entry, and then click Modify.
   6. In the Value data box, type D2, and then click OK.
   7. On the File menu, click Exit.
   8. At the command prompt, type the following command, and then press ENTER:
      net start ntfrs

Windows Update Error Code 800B0001

When trying to update Server 2012 you may see the error below when using WSUS 3.0 SP2.


To fix the above issue there is an update for Windows Server Update Services 3.0 Service Pack 2 that is available. Download it from below link.
http://support.microsoft.com/default.aspx?scid=kb;en-us;2720211

Once downloaded just run the setup file



Check for updates again..


In my experience this fixes the problem every time.

If you'd rather use the Microsoft Fix it then use THIS link.  The reference page can be found at http://support.microsoft.com/kb/822798

Good luck!

Make Your Own Start Button for Windows Server 2012

I know many of you have experienced the frustration of not having a start menu with Windows 8 and Windows 2012.  

This is especially a pain in an RDP session because you have to find that one pixel to click on to bring up the start menu.  I found this easy to use shortcut that gives you a quick link to the Windows 2012 or Win 8 start menu. 

-          Simply create a shortcut and point it to the following path. 

  explorer.exe shell:::{2559a1f8-21d7-11d4-bdaf-00c04f60b9f0}

-          Set a pretty icon from imageres.dll, and then pin this to the taskbar.  BAM!  Instant Start button.

 

There are also applications like Start8 by StartDock ($5 program) or Windows 8 Start menu that you can download from www.ninite.com that you may want to look at too.  

This only takes a couple of minutes to put together and makes all the difference when working with these operating systems

How to Enable Server 2012 Deduplication

Borrowed from HERE:

Deduplication is a new feature in Windows Server 2012, which deduplicates files at a block level on Windows Server 2012 File Servers. 

To enable Deduplication on a Windows Server 2012 File Server, do the following:

1. Open Windows Server 2012 Server Manager
2. Install the Data Deduplication role and associated required role services (It’s actually a role: File And Storage Services -> File Services -> File Server)
3. In Windows Server 2012 Server Manager, click on File and Storage Services
4. Right click on the server and click Deduplication Schedule
5. Set-up the required deduplicaton schedule (Background optimization may be sufficient) and click OK
6. In Windows Server 2012 Server Manager, under Volumes, right click the volume you would like to enable Deduplication on and click Enable Deduplication.
7. Tick the box to enable data duplication. You may wish to change the number of days that the files have to be older than to be deduplicated and set any specific file or folder exclusions before clicking OK

You now know how to enable data Deduplication in Windows Server 2012 File Server. But to see deduplication happening on your volume, you have to wait for the schedule to run (or wait for the background optimization to finish). Alternatively, you can kick start deduplication using PowerShell commands.

To manage Deduplication from the PowerShell, in Windows Server 2012 Server Manager, click Tools (at the top right hand corner) and Windows PowerShell ISE. Next, import the PowerShell Deduplication module with this command: Import-Module Deduplication

To see how many files have been deduplicated and how much data has been saved, type:

Get-DedupStatus

To start the deduplication job, type:

Start-DedupJob -Type Optimization  -Volume X

Where X is theletter of the volume you want to deduplicate, ie. X could equal e:  (Note that you must have enabled deduplication prior to running this). You will then be able to check the status of the deduplication job by running the following PowerShell command:

Get-DedupJob

That's all there is to it.  Leave me comments if you have any questions or concerns.

Show Hidden Network Devices in Windows Server

This happens all too often when I'm working on servers that have been through P2V or had their network adapters changed for some reason.  To work around this behavior and display devices when you click Show hidden devices:

1. Click Start, point to All Programs, point to Accessories, and then click Command Prompt.
2. At a command prompt, type the following command , and then press ENTER:
   set devmgr_show_nonpresent_devices=1
3. Type the following command a command prompt, and then press ENTER:
   start devmgmt.msc
4. Troubleshoot the devices and drivers in Device Manager.
   
   NOTE: Click Show hidden devices on the View menu in Device Managers before you can see devices that are not connected to the computer.
5. When you finish troubleshooting, close Device Manager.
6. Type exit at the command prompt.

Moving DHCP to Server 2012

I've just setup a couple of new 2012 Standard Domain Controllers for a customer and I wanted to be able to take advantage of the DHCP failover for them.  Their old Domain Controller were Server 2003 so I did a bit of research and here's how I moved it in just a couple of minutes.

Once this process is done all that remains is to deauthorize your old DHCP setup and then configure DHCP failover in Server 2012.  Easy!

To move a DHCP database and configuration from a server that is running Windows Server 2003 to another server that is running Windows Server 2012

1. Log on to the source DHCP server.
   
2. Click Start, click Run, type cmd in the Open box, and then click OK.
3. Type netsh dhcp server export C:\dhcp.txt all, and then press ENTER.
   
4. Install the DHCP server service on the destination DHCP server.
   
5. Log on to the destination DHCP server.
   
6. Copy the exported DHCP database file to the local hard disk of the destination DHCP server.
   
7. Verify that the DHCP service is started on the destination DHCP server.
   
8. Click Start, click Run, type cmd in the Open box, and then click OK.
   
9. 10. Type netsh dhcp server import C:\dhcp.txt all, and then press ENTER
   
10. Open DHCP.
    
11. In the console tree, click DHCP.
    
12. On the Action menu, click Authorize