<div>
We have applied that update, and re-syncro'd -- Waiting for the changes to take affect and I will let you know.<br />
<br />
Thanks!
</div>


We have applied that update, and re-syncro'd -- Waiting for the changes to take affect and I will let you know.

Thanks!

<div>
<div class="content wysiwyg-content">
We are running Microsoft Hyper-V 2012 (core), and it is assigned via AD &amp;&nbsp;Group Policy (client side targeting) to check in to our WSUS server (which is running WSUS 3.2).. it is checking in as &quot;Microsoft Windows Server 2003 Standard X64 Edition&quot; which is wrong.<br />
<br />
Update's are set to automatic I believe within Hyper-V core 2012.<br />
<br />
What things need to be changed so that it checks in regularly, and is reporting correctly?<br />
<a href="https://filedb.experts-exchange.com/incoming/2013/06_w25/661719/Greenshot-2013-06-21-13-38-37.png" target="_blank" class="file-inline" title="WSUS Server showing misinformation (22 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>Greenshot-2013-06-21-13-38-37.png</a>
</div>
</div>


Greenshot-2013-06-21-13-38-37.png

We are running Microsoft Hyper-V 2012 (core), and it is assigned via AD & Group Policy (client side targeting) to check in to our WSUS server (which is running WSUS 3.2).. it is checking in as "Microsoft Windows Server 2003 Standard X64 Edition" which is wrong.

Update's are set to automatic I believe within Hyper-V core 2012.

What things need to be changed so that it checks in regularly, and is reporting correctly?

Hyper-V Server Core 2012 checks into WSUS as Windows Server 2003

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

Microsoft Virtual Server was a virtualization solution that facilitated the creation of virtual machines on the Windows XP, Windows Vista and Windows Server 2003 operating systems. Virtual machines are created and managed through a web-based interface that relies on Internet Information Services (IIS) or through a Windows client application tool called VMRCplus. Features included Linux guest operating system support, Virtual Disk Precompactor, symmetric multiprocessing (SMP), x64 host operating system support, the ability to mount virtual hard drives on the host machine and additional operating systems support, including Windows Vista, and a volume shadow copy writer.

Microsoft Virtual Server

Microsoft applications include a variety of software programs, including development and digital authoring programs (Expression and Media Center), educational programs, Internet software, including Essentials, Skype and the Live family, anti-virus, productivity applications and suites like Office, Excel, Word, Outlook, Access and PowerPoint, video games and server applications such as Exchange, SharePoint, IIS and Virtual Server.

Microsoft Applications

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.