Showing posts with label Windows Server 2012. Show all posts
Showing posts with label Windows Server 2012. Show all posts

Friday, March 20, 2015

VMware Paravirtual Driver - Windows 2012 Installation

One day you may find yourself installing a Windows 2012 Server and wanting to use the VMware Paravirtual driver for the vSCSI controller for the disks.  The VMware KB article on this covers this topic very well.

1. Create a new VM
2. Remove the Hard disk 1 and click OK
3. Add a Hard disk and then click Change Type for SCSI Controller Type
4. Choose VMware Paravirtual and click OK and then OK again
5. During the Windows Installation Setup, you'll need to load the VMware Paravirtual SCSI driver.  Attach the floppy image to the VM using the "Connect to floppy image on a datastore..." option.
There will be a folder named "vmimages" then "floppies" and select the "pvscsi-Windows2008.flp" file and click OK.
6. Click on Load driver and then click on Browse
7. Select the "amd64" folder under the Floppy Disk Drive

8. Click Next
9. The disk is now present and you can continue with the Windows 2012 Setup

Wednesday, May 7, 2014

Installing Operations Manager 2012 R2 agent fails with error code 80070005

Today, I ran into an issue when trying to install the SCOM 2012 R2 agent on a domain controller running Windows Server 2012 R2.  I found the following technet article which proved useful as it had the error and error code I was getting, but the remediation steps didn't solve my problem.

Troubleshooting Issues When You Use the Discovery Wizard to Install an Agent

Upon further investigation, I could not access the SYSVOL and NETLOGON shares on that specific domain controller from the SCOM management servers running Windows Server 2012 R2.

I remember seeing this sort of issue when accessing shares on a NetApp that we have from a Windows 2012 Server.  So disabling the secure negotiate on the Windows 2012 Server solved that issue.  So I did the same on the SCOM Management Servers which ended up fixing this issue using the following powershell command.

Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters" RequireSecureNegotiate -Value 0 -Force
 http://support.microsoft.com/kb/2686098

You should also read this which explains Secure Negotiate which is new for SMB3.
http://blogs.msdn.com/b/openspecification/archive/2012/06/28/smb3-secure-dialect-negotiation.aspx