Server 2012 R2 Hyper-V Client won't connect to Host.
Hi I have a server with 2012 R2 and Hyper-V is installed. I have set my VM's up and everything on the server is working perfectly. I installed the hyper-v role on my Win 7 x64 machine and it will not connect to my server. I ended up calling in to microsoft
and they have determined it's a bug. I really need a work around does anyone know of a work around?
Thanks,
DB
Hi,
You can install the Windows Management Framework 4.0, then use PowerShell to manage the Hyper-V.
More information:
Windows Management Framework 4.0
http://www.microsoft.com/en-us/download/details.aspx?id=40855
Hyper-V Cmdlets in Windows PowerShell
http://technet.microsoft.com/en-us/library/hh848559.aspx
The third party related article:
How to install Windows PowerShell 4.0
http://blog.powershell.no/category/windows-server-2012-r2/
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.
Similar Messages
-
Could you please share your best practices for setting up a new Windows Server 2012 r2 Hyper-V Virtualized AD DC, that will be running on a new WinSrv 2012 r2 host server. (This
will be for a brand new network setup, new forest, domain, etc.)
Specifically, your best practices regarding:
the sizing of non virtual and virtual volumes/partitions/drives,
the use of sysvol, logs, & data volumes/drives on hosts & guests,
RAID levels for the host and the guest(s),
IDE vs SCSI and drivers both non virtual and virtual and the booting there of,
disk caching settings on both host and guests.
Thanks so much for any information you can share.A bit of non essential additional info:
We are small to midrange school district who, after close to 20 years on Novell networks, have decided to design and create a new Microsoft network and migrate all of our data and services
over to the new infrastructure . We are planning on rolling out 2012 r2 servers with as much Hyper-v virtualization as possible.
During the last few weeks we have been able to find most of the information we need to undergo this project, and most of the information was pretty solid with little ambiguity, except for
information regarding virtualizing the DCs, which as been a bit inconsistent.
Yes, we have read all the documents that most of these posts tend point to, but found some, if not most are still are referring to performing this under Srvr 2008 r2, and haven’t really
seen all that much on Srvr2012 r2.
We have read these and others:
Introduction to Active Directory Domain Services (AD DS) Virtualization (Level 100),
Virtualized Domain Controller Technical Reference (Level 300),
Virtualized Domain Controller Cloning Test Guidance for Application Vendors,
Support for using Hyper-V Replica for virtualized domain controllers.
Again, thanks for any information, best practices, cookie cutter or otherwise that you can share.
Chas. -
Server 2012 R2 Hyper-V Cluster, VM blue screens after migration between nodes.
I currently have a two node Server 2012 R2 Hyper-v Cluster (fully patched) with a Windows Server 2012 R2 Iscsi target.
The VMs run fine all day long, but when I try to do a live/quick migration the VM blue screens after about 20 minutes. The blue reports back about a “Critical_Structure_Corruption”.
I’m being to think it might be down to CPU, as one system has an E-2640v2 and the other one has an E5-2670v3. Should I be able to migrate between these two systems with these type of CPU?
TimSorry Tim, is that all 50 blue screen if live migrated?
Are they all on the latest integration services? Does a cluster validation complete successfully? Are the hosts patched to the same level?
The fact that if you power them off then migrate them and they boot fine, does point to a processor incompatibility and the memory BIN file is not accepted on the new host.
Bit of a long shot but the only other thing I can think of off the top of my head if the compatibility option is checked, is checking the location of the BIN file when the VM is running to make sure its in the same place as the VHD\VHDX in the
CSV storage where the VM is located and not on the local host somewhere like C:\program data\.... that is stopping it being migrated to the new host when the VM is live migrated.
Kind Regards
Michael Coutanche
Blog:
Twitter: LinkedIn:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose. -
Server 2012 r2 Hyper-v guest network speed with 10 GB NIC's
Hi
Setting up a Server 2012 r2 Hyper-v host with an onboard 4 port 1 GB nic and a offboard dual port 10 GB nic. We are using the 1gb quad port for management. The 10 Gb we intend using for hyper-v guest use however we don't seem to be able to achieve very high
speeds though the 10 GB adapter when assigned to a virtual switch. Testing the 10 Gb nic from the host confirms that we can transfer/get 10 GB speeds. When assigned to a virtual switch however the speed drops to about 1-2 Gbps. Has anybody seen anything like
this ?. We've tried a variety of settings and i can confirm that the network traffic is using the 10 GB nic.Hi,
I am almost certain what you see is by design. I don't want to go into to much detail because I'm in a bit of a hurry. But allow me to explain.
Suppose you have a 10Gb NIC interface and an multi-core CPU. When you have RSS (Receive-Side Scaling) disabled a single core can normally handing
around 2.5-4.3Gbps. When you enable RSS the data streams/traffic is spread across multiple cores.
But RSS is a network optimization feature for the Management OS, not for a vSwitch. Instead you should use VMQ (Virtual Machine Queuing). VMQ is
the equilavant of RSS, but then intended for VMs. But... there is a difference. VMQ does not spread single data streams/traffic across multiple cores. Instead is (dynamically) assigns each vmNIC its own core. So... you don't use multiple-cores at a time for
a single vmNIC. You can't use RSS and VMQ at the same time. Keep that in mind.
But... you can accomplish this by enabling vRSS as well. That's another story.
If you watch the following video, at the end you know all about VMQ.
Hyper-V dVMQ
http://www.hypervrockstar.com/tag/dvmq/
Boudewijn Plomp | BPMi Infrastructure & Security
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember, if you see a post that helped you please click "Vote as Helpful", and if it answered your question, please click "Mark as Answer". -
Does Windows Server 2012 support Remote Desktop Client 6.1?
Hi,
Does Windows Server 2012 support Remote Desktop Client 6.1? IU can't find a link anywhere on the Microsoft site to confirm this!
Thanks,
Jimthis should help you
http://social.technet.microsoft.com/Forums/windowsserver/en-US/b664ddaf-6c11-49e2-8a69-0df3b8ef13a1/server-2012r2-rds-farm-with-xp-and-windows-vista-clients?forum=winserverTS -
I have been
troubleshooting a very strange issue with Lync clients being unable to connect
to a conference via dial-in number when the conference is hosted on a different
pool. This happens internally and there is no media gateway or SIP trunk
involved.<o:p></o:p>
Users are
unable to join a conference from Polycom CX phones and Lync 2013/2010 software clients
by dialling conference Dial-in number which is located on a different pool than
actual conference. Users are prompted to input their conference ID, however,
they are never connected to the conference (10 min silence followed by error
announcement). <o:p></o:p>
This only
happens if the dial-in number is homed on a different pool than conference.
Both pools are Lync 2013 Standard Edition running on Windows Server 2012.
Servers and clients are patched with the latest CU.<o:p></o:p>
I noticed that
when you call dial-in number’s SIP address, user will get transferred to a
conference (works ok). When you dial just a number users is never transferred
and RT Audio traffic still goes directly to a server which is hosting dial-in
number.<o:p></o:p>
After
checking Lync traces it looks like Lync client ignores the REFER message from
the FE server hosting Dial-in number and it never send an INVITE to the server
whit active conference.<o:p></o:p>
The only difference
between INVITES for working calls and calls that failed to connect to the
conference is the presence of the user=phone in TO header:<o:p></o:p>
Working
invite:<o:p></o:p>
TO:
<sip:[email protected]><o:p></o:p>
Failed invite:Please try to disable refer support for all pools.
The problem seems occur when Attendant transfer the call to another pool.
Please provide more trace file information.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
VMM Agent install fails on Windows Server 2012 R2 Hyper-V
Hi,
We are unable to install VMM 2012 R2 agent on Windows Server 2012 R2 server either from VMM console or manually on the hyper-v server.
Error on VMM Console:
Error (410)
Agent installation failed on chsicoecdh03.casper.com.
Fatal error during installation (0x80070643)
Recommended Action
Try the operation again. If the problem persists, install the agent locally and then add the managed computer.
==================================================================
Error on Hyper-v server:
MSI (c) (E8:D0) [16:53:24:726]: Windows Installer installed the product. Product Name: Microsoft System Center Virtual Machine Manager Agent (x64). Product Version: 3.2.7510.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success
or error status: 1603.
Also, I suspect may be issue with WMI then checked WMI repository and it is in consistent state. winmgmt /verifyrepository.
Please help on this issue.
Any help would be appreciated.
Thanks
Kumaresan LakshmananSo, I've managed to research this some more since Thursday and I've come to the conclusion that Hyper-V does a horrible job of supporting Qualcomm NIC cards. That's the only thing I can conclude as far as where the issue is originating. I've read many
post and walkthroughs but nothing that has helped. The issue wasn't with any settings in the domain controller. The issue was that there really is a slow connection originating at the domain controller that is a VM and has network connectivity through the
virtual switch from Hyper-V. So, next question is, how do I get the DC to have better connectivity through the NIC that Hyper-V won't give it? If hyper-v would allow passthrough, this would be so much simpler. VM-ware is looking really good at this point.
Im disappointed in MS right now. -
I have racked my brain and done everything that I know to do for about two weeks now. I am setting up a new system at our fire department and I am having the worst luck with getting the workstations to login to the domain controller with roaming
profiles. It keeps telling me that the roaming profile could not be loaded because of a slow connection. These are workstations that are connected directly to the switch that the DC is connected to. I have tried multiple connections regarding
the layout (DC into the router, router into the switch). The router is a Cisco RV220W. I have two VLANS, one for public and one for private domain. The Private VLAN has DHCP turned off since I am providing it through the DC. I currently
have a connection from the Private VLAN going to the unmanaged switch that the workstations and server are plugged into.
The server is a Dell PowerEdge R420 that has 6 NIC ports (1 dual port and 1 quad port). I have a virtual switch setup on Hyper-V for an external port (let's say Card 2 Port 3) that is assigned to the WS 2012R2 Domain Controller. The DC can see
the internet fine and the workstations can connect to the shared folders on the server. I can retrieve files by just using the computer name or FQDN. The DC is also running DNS and DHCP. The DNS has the _msdcs setup from when I installed
the active directory role. I have attempted to assign static IP addresses to the workstations:
IP: 10.0.0.80
Subnet: 255.255.255.0
IPV4 Gateway: 10.0.0.1
IPV4 DNS: 10.0.0.12
I've attempted "append the specific DNS suffix", I've "registered the connection in DNS", I've used "use this connections suffix in DNS registration".
The server is assigned:
IP: 10.0.0.12
Subnet: 255.255.255.0
IPV4 Gateway: 10.0.0.1
IPV4 DNS: 10.0.0.12
The DNS entries have forwarders that forward to my ISP DNS servers for lookup
I've enabled and disabled DHCP, I've installed a new VM just to create another DC to make sure that I didn't goof up when I created it.
I've lost my patience with this project and am sinking fast. Can someone please offer some advice as to what I've done wrong? I've created this exact scenario at work many times but, I've never done it with Windows Server 2012. Is this
possibly something to do with the Dell PowerEdge server (Generation 12) with the SR-IOV? I am going to attempt to work on it some more tomorrow when I get over there. I think there may be an issue with the SR-IOV not being enabled on the machine
through the Dell Bios. Would the SR-IOV really cause the workstations to report a slow connection? When I login at the domain controller the roaming profiles and folder redirection work fine so, I know the GPO settings are correct. I don't
have "ignore slow connections" or any of those GPO's set. I need to get it working the correct way so, I didn't want to fool the server when there is another underlying problem. Any help that someone can offer, I am more than willing
to listen. If you need more information, please ask.
Thanks,
JaySo, I've managed to research this some more since Thursday and I've come to the conclusion that Hyper-V does a horrible job of supporting Qualcomm NIC cards. That's the only thing I can conclude as far as where the issue is originating. I've read many
post and walkthroughs but nothing that has helped. The issue wasn't with any settings in the domain controller. The issue was that there really is a slow connection originating at the domain controller that is a VM and has network connectivity through the
virtual switch from Hyper-V. So, next question is, how do I get the DC to have better connectivity through the NIC that Hyper-V won't give it? If hyper-v would allow passthrough, this would be so much simpler. VM-ware is looking really good at this point.
Im disappointed in MS right now. -
I need to split the load of my WSUS on to another site because the amount of computers is straining the internet connection in the amount of uploads performed.
However I'm having an issue at the second WSUS where only Windows 7 and Server 2003 clients will update...
Windows 8.1 and Server 2008 and Server2012 won't update giving the following error codes: 8024400A and 80072EE2
The WSUS is a Server 2012 with Local Update Publisher 1.1 installed. It works fine locally at the site but not across our WAN.
The clients appear in the WSUS console but fail to check for updates.
I've tried it with the firewall turned off...
Both WSUS servers are using Microsoft SCEP 2012.
Has anyone out there experienced this? Or have any suggestions to fix?
Cheers.Hi there,
I spoke too soon, I think I got one Windows 8 client to update yesterday by fluke. Now today it won't.
There's not much different between the W7 and W8 systems they both use the same antivirus. Same software but updated on W8.
Here is the windows update.log:
2014-06-05 10:44:14:561
976 954
Misc =========== Logging initialized (build: 7.9.9600.17093, tz: +1000) ===========
2014-06-05 10:44:14:639
976 954
Misc = Process: C:\Windows\system32\svchost.exe
2014-06-05 10:44:14:639
976 954
Misc = Module: c:\windows\system32\wuaueng.dll
2014-06-05 10:44:14:561
976 954
Service *************
2014-06-05 10:44:14:639
976 954
Service ** START ** Service: Service startup
2014-06-05 10:44:14:639
976 954
Service *********
2014-06-05 10:44:15:311
976 954
IdleTmr Non-AoAc machine. Aoac operations will be ignored.
2014-06-05 10:44:15:311
976 954
Agent * WU client version 7.9.9600.17093
2014-06-05 10:44:15:326
976 954
Agent WARNING: SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
2014-06-05 10:44:15:326
976 954
Agent * Base directory: C:\Windows\SoftwareDistribution
2014-06-05 10:44:15:326
976 954
Agent * Access type: No proxy
2014-06-05 10:44:15:326
976 954
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2014-06-05 10:44:15:326
976 954
Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2014-06-05 10:44:15:326
976 954
Agent * Network state: Connected
2014-06-05 10:44:15:326
976 954
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2014-06-05 10:44:15:326
976 954
Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2014-06-05 10:44:16:123
976 954
Agent *********** Agent: Initializing global settings cache ***********
2014-06-05 10:44:16:123
976 954
Agent * Endpoint Provider: 00000000-0000-0000-0000-000000000000
2014-06-05 10:44:16:123
976 954
Agent * WSUS server: http://10.155.194.59:8530
2014-06-05 10:44:16:123
976 954
Agent * WSUS status server: http://10.155.194.59:8530
2014-06-05 10:44:16:123
976 954
Agent * Target group: Test Group
2014-06-05 10:44:16:123
976 954
Agent * Windows Update access disabled: No
2014-06-05 10:44:16:170
976 954
WuTask WuTaskManager delay initialize completed successfully..
2014-06-05 10:44:16:170
976 954
AU Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2014-06-05 00:24:13, not idle-only, not network-only
2014-06-05 10:44:16:170
976 954
AU Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2014-06-05 05:36:25, not idle-only, not network-only
2014-06-05 10:44:16:170
976 954
AU Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2014-06-05 05:36:25, not idle-only, not network-only
2014-06-05 10:44:16:170
976 954
Report CWERReporter::Init succeeded
2014-06-05 10:44:16:170
976 954
Agent *********** Agent: Initializing Windows Update Agent ***********
2014-06-05 10:44:16:170
976 954
DnldMgr Download manager restoring 0 downloads
2014-06-05 10:44:16:170
976 954
AU ########### AU: Initializing Automatic Updates ###########
2014-06-05 10:44:16:170
976 954
AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Scheduled} added to AU services list
2014-06-05 10:44:16:170
976 954
AU AIR Mode is disabled
2014-06-05 10:44:16:170
976 954
AU # Policy Driven Provider: http://10.155.194.59:8530
2014-06-05 10:44:16:170
976 954
AU # Detection frequency: 22
2014-06-05 10:44:16:170
976 954
AU # Target group: Test Group
2014-06-05 10:44:16:170
976 954
AU # Approval type: Scheduled (Policy)
2014-06-05 10:44:16:170
976 954
AU # Auto-install minor updates: Yes (Policy)
2014-06-05 10:44:16:170
976 954
AU # ServiceTypeDefault: Service 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782 Approval type: (Scheduled)
2014-06-05 10:44:16:170
976 954
AU # Will interact with non-admins (Non-admins are elevated (Policy))
2014-06-05 10:44:16:186
976 954
AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80070032
2014-06-05 10:44:16:186
976 954
AU AU finished delayed initialization
2014-06-05 10:44:16:202
976 954
AU Adding timer:
2014-06-05 10:44:16:202
976 954
AU Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2014-06-05 03:47:12, not idle-only, not network-only
2014-06-05 10:44:16:217
976 99c
DnldMgr Asking handlers to reconcile their sandboxes
2014-06-05 10:45:17:562
976 954
AU ReAttemptDownloadsAsUserIfNecessary, No calls in download progress.
2014-06-05 10:45:31:453
976 778
IdleTmr Incremented idle timer priority operation counter to 1
2014-06-05 10:45:34:562
976 778
AU Triggering AU detection through DetectNow API
2014-06-05 10:45:34:562
976 778
AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Scheduled} added to AU services list
2014-06-05 10:45:34:562
976 778
AU Triggering Online detection (interactive)
2014-06-05 10:45:34:562
976 778
AU Adding timer:
2014-06-05 10:45:34:562
976 778
AU Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2014-06-05 00:45:34, not idle-only, not network-only
2014-06-05 10:45:34:609
976 954
AU #############
2014-06-05 10:45:34:609
976 954
AU ## START ## AU: Search for updates
2014-06-05 10:45:34:609
976 954
AU #########
2014-06-05 10:45:34:609
976 954
AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Scheduled} added to AU services list
2014-06-05 10:45:34:609
976 954
IdleTmr WU operation (CSearchCall::Init ID 1) started; operation # 15; does use network; is not at background priority
2014-06-05 10:45:34:609
976 954
IdleTmr Incremented idle timer priority operation counter to 2
2014-06-05 10:45:34:797
976 954
Report *********** Report: Initializing static reporting data ***********
2014-06-05 10:45:34:797
976 954
Report * OS Version = 6.3.9600.0.0.65792
2014-06-05 10:45:34:797
976 954
Report * OS Product Type = 0x00000004
2014-06-05 10:45:34:813
976 954
Report * Computer Brand = Microsoft Corporation
2014-06-05 10:45:34:813
976 954
Report * Computer Model = Virtual Machine
2014-06-05 10:45:34:813
976 954
Report * Platform Role = 1
2014-06-05 10:45:34:813
976 954
Report * AlwaysOn/AlwaysConnected (AOAC) = 0
2014-06-05 10:45:34:813
976 954
Report * Bios Revision = 090004
2014-06-05 10:45:34:813
976 954
Report * Bios Name = BIOS Date: 03/19/09 22:51:32 Ver: 09.00.04
2014-06-05 10:45:34:813
976 954
Report * Bios Release Date = 2009-03-19T00:00:00
2014-06-05 10:45:34:813
976 954
Report * Bios Sku Number unavailable.
2014-06-05 10:45:34:813
976 954
Report * Bios Vendor = American Megatrends Inc.
2014-06-05 10:45:34:813
976 954
Report * Bios Family unavailable.
2014-06-05 10:45:34:828
976 954
Report * Bios Major Release unavailable.
2014-06-05 10:45:34:828
976 954
Report * Bios Minor Release unavailable.
2014-06-05 10:45:34:828
976 954
Report * Locale ID = 3081
2014-06-05 10:45:35:578
976 954
Agent *** START *** Queueing Finding updates [CallerId = AutomaticUpdatesWuApp Id = 1]
2014-06-05 10:45:35:609
976 954
AU <<## SUBMITTED ## AU: Search for updates [CallId = {CDA6DEA2-9874-4DB5-AAA7-9A05D933C012} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
2014-06-05 10:45:35:609
976 fc4
Agent *** END *** Queueing Finding updates [CallerId = AutomaticUpdatesWuApp Id = 1]
2014-06-05 10:45:35:609
976 fc4
Agent *************
2014-06-05 10:45:35:609
976 fc4
Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdatesWuApp Id = 1]
2014-06-05 10:45:35:609
976 fc4
Agent *********
2014-06-05 10:45:35:609
976 fc4
Agent * Online = Yes; Ignore download priority = No
2014-06-05 10:45:35:609
976 fc4
Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0
and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-06-05 10:45:35:609
976 fc4
Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2014-06-05 10:45:35:609
976 fc4
Agent * Search Scope = {Machine & All Users}
2014-06-05 10:45:35:609
976 fc4
Agent * Caller SID for Applicability: S-1-5-21-1323361640-3159480285-1943353560-1532
2014-06-05 10:45:35:609
976 fc4
Agent * RegisterService is set
2014-06-05 10:45:35:625
976 fc4
EP Got WSUS Client/Server URL: "http://10.155.194.59:8530/ClientWebService/client.asmx"
2014-06-05 10:45:35:641
976 fc4
Setup Checking for agent SelfUpdate
2014-06-05 10:45:35:641
976 fc4
Setup Client version: Core: 7.9.9600.17093 Aux: 7.9.9600.17093
2014-06-05 10:45:35:641
976 fc4
EP Got WSUS SelfUpdate URL: "http://10.155.194.59:8530/selfupdate"
2014-06-05 10:45:35:672
976 fc4
Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
2014-06-05 10:45:35:734
976 fc4
Misc Microsoft signed: NA
2014-06-05 10:45:35:734
976 fc4
Misc Infrastructure signed: Yes
2014-06-05 10:45:35:734
976 fc4
Misc WARNING: Cab does not contain correct inner CAB file.
2014-06-05 10:45:35:734
976 fc4
Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
2014-06-05 10:45:35:734
976 fc4
Misc Microsoft signed: NA
2014-06-05 10:45:35:750
976 fc4
Misc Infrastructure signed: Yes
2014-06-05 10:45:35:766
976 fc4
Setup Skipping SelfUpdate check based on the /SKIP directive in wuident
2014-06-05 10:45:35:766
976 fc4
Setup SelfUpdate check completed. SelfUpdate is NOT required.
2014-06-05 10:45:35:907
976 fc4
PT +++++++++++ PT: Synchronizing server updates +++++++++++
--continued-- -
SAN Storage solution in combination w/ Server 2012 R2 (HYPER-V)
Hello everyone,
We are currently in talks with 2 storage vendors (IBM and NETAPP) in order to replace/expand our current SAN storage and finally make the move to a virtualized environment (HYPER-V).
For the NETAPP side, they proposed a FAS3220 for our main location and a FAS2240 for our DR location, both running Clustered ONTAP 8.2. For the IBM side, they proposed a couple of V3700's (under SVC).
I'm aware this isn't the place to discuss these things in depth, but could anyone who has any experience w/ both solutions in combination w/ Server 2012 (R2) and HYPER-V recommend one solution over the other? Or is anyone in possession of a feature list
for both solutions?
Any help will be greatly appreciated.
With Kind Regard,
L.Hello everyone,
We are currently in talks with 2 storage vendors (IBM and NETAPP) in order to replace/expand our current SAN storage and finally make the move to a virtualized environment (HYPER-V).
For the NETAPP side, they proposed a FAS3220 for our main location and a FAS2240 for our DR location, both running Clustered ONTAP 8.2. For the IBM side, they proposed a couple of V3700's (under SVC).
I'm aware this isn't the place to discuss these things in depth, but could anyone who has any experience w/ both solutions in combination w/ Server 2012 (R2) and HYPER-V recommend one solution over the other? Or is anyone in possession of a feature list
for both solutions?
Any help will be greatly appreciated.
With Kind Regard,
L.
You should avoid NetApp when thinking about Hyper-V deployment. For a reason: NetApp "internals" are a pure filer built around WAFL and NFS being a direct interface to it. So for environments where you need to talk NFS (VMware ESXi and any *nixes with a good
client NFS implementation) NetApp really shines. As Hyper-V has no support for NFS in terms of a VMs storage and pretty much never will, Windows having very low performing NFS support as a client (latency is ridiculous, 10x-100x times higher compared to FreeBSD
running on the same hardware) and iSCSI with NetApp is a bolt-on solution (basically it's a file on a local WAFL partition and iSCSI uplink) you're not going to have the best performance and good features coverage. Up to the point when NetApp would do SMB
3.0 in production for a couple of years. So picking up between IBM and NetApp in your case assuming these are only two options - go IBM. If you need a SAN for your environment and can think twice - think about virtual SAN. That's what big hypervisor boys are
doing.
StarWind iSCSI SAN & NAS -
Windows Server 2012 R2 Hyper V on a SBS 2011 Domain replication failure
I have a SBS 2011 Domain which I am adding two 2012 R2 Standard servers in order to facilitate virtualization and consolidate physical servers. I have the two 2012 R2 servers up and running and a test server running virtually on Hyper-V. I want
to test replication from one Hyper-V host to the other, however, I am unable to setup Kerberos delegation in the SBS 2011 AD domain. Specifically, the Service Type of Microsoft Virtual System Migration Service is not listed. CIFS is available,
however, there are no Service Types having to do with Hyper-V available.
I have upgraded the AD using adprep from the 2012 R2 installation disc, however, this has not added the service types.
Thank you in advance for the help!Hi Justin,
Thank you for the information. I had originally reviewed the article you mentioned in your reply, however, this did not work for me. It accurately described the problem I am having, however, the solution did not work.
I did a little review of the syntax of the command SETSPN and found that the article referenced above has a "/" instead of a "\" in the command line. When I modified my syntax to reflect using the forward slash, the command seemed to processed
correctly, however, when I go back to the delegation steps, the service name is still not there. I did verify the service was registered properly by listing out all the SPN registrations.
Clarifying Question: Based on the command I ran to add this Service, I am wondering if I used the correct servers. Basically, I have the following:
Server 1 - SBS 2011 domain controller
Server 2 - 2012 R2 Hyper-V Server
Server 3 - 2012 R2 Hyper-V Server
I want to setup this Kerberos delegation for CIFS and Microsoft Virtual System Migration on Server 2 and 3 and am setting this up using ADUC on Server 1. I ran the SETSPN command on Server 1 for Server 1 - was this the correct thing to do or should
I have an SPN entry for Server 2 and/or 3?
Sorry for what is probably a very basic question.
Thank you again for your help. -
Server 2012 R2 Hyper-V Cluster - Losing connectivity to vLANs
Hi Everybody,
I am experiencing a strange issue with a Server 2012 R2 Hypervisor. There are two physical NICs teamed (one from on-board and one from expansion board), this team is assigned to a hyper-v virtual switch, there are four virtual network adapters
assigned to the switch (Backend, Heartbeat, Management & CSV/Live Migration).
The server has been running without issue for months but, all of a sudden has started to lose connectivity to the Backend and Heartbeat. The loss of connection only occurs once VMs are hosted on the server and it doesn't happen immediately, it can take
anywhere from 12 hours to several days.
There are no errors on the NICs or vNICs themselves and the configuration is intact. Once connectivity is lost to the Backend and Heartbeat, it remains that way and it seems the only solution so far is to reboot the server. Hardware diagnostics have been
run and revealed no issues. There are no useful events in event viewer, the alerts relate to the loss of connection to the cluster as a result of connectivity being lost on the Backend and Heartbeat.
I have 6 other hypervisors with the same network configuration that are performing without issue so, I don't believe the problem is the configuration. The only difference is the hypervisor that has the problems is a Dell Poweredge R620 and the other 6 are
Dell PowerEdge R610s.
Can anyone advise what might be the cause of these issues or, any event logging to enable that might help isolate where the issue lies.Sorry Tim, is that all 50 blue screen if live migrated?
Are they all on the latest integration services? Does a cluster validation complete successfully? Are the hosts patched to the same level?
The fact that if you power them off then migrate them and they boot fine, does point to a processor incompatibility and the memory BIN file is not accepted on the new host.
Bit of a long shot but the only other thing I can think of off the top of my head if the compatibility option is checked, is checking the location of the BIN file when the VM is running to make sure its in the same place as the VHD\VHDX in the
CSV storage where the VM is located and not on the local host somewhere like C:\program data\.... that is stopping it being migrated to the new host when the VM is live migrated.
Kind Regards
Michael Coutanche
Blog:
Twitter: LinkedIn:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose. -
New WSUS on Server 2012 - problem with win8 clients
Hi,
Two weeks ago we created a new Server 2012 and installed the WSUS role from scratch on it. Its version number is: 6.2.9200.16384. It replaced a Server 2008 WSUS server. After some time all the win7 clients updated and reported as
they did on the old and replaced server.
However all our win8 clients refuse to update against this server. They show correctly up in WSUS server console each with 107 needed updates day after day. We have rebooted them and done numerous wuauclt /resetauthorization /detectnow and wuauclt
/detectnow /reportnow, but to no avail.
I paste in some lines from a win8 client winupdate log at the end of this message if someone can figure out what I have to do to get these clients update as they did against the old wsus server. Thanks for help on this issue.
regards Tor
2014-02-03 08:33:38:008 920 153c Agent *************
2014-02-03 08:33:38:008 920 153c Agent ** START ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03 08:33:38:008 920 153c Agent *********
2014-02-03 08:33:38:008 920 153c Agent * Online = Yes; Ignore download priority = No
2014-02-03 08:33:38:008 920 153c Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-02-03 08:33:38:008 920 153c Agent * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-02-03 08:33:38:008 920 153c Agent * Search Scope = {Machine & All Users}
2014-02-03 08:33:38:008 920 153c Agent * Caller SID for Applicability: S-1-5-18
2014-02-03 08:33:38:008 920 153c Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
2014-02-03 08:33:38:008 920 1990 AU >>## RESUMED ## AU: Search for updates [CallId = {ABC7E77F-635F-4192-9B92-CBF9B1CB8AB0} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
2014-02-03 08:33:38:008 920 1990 AU # 0 updates detected
2014-02-03 08:33:38:008 920 1990 AU #########
2014-02-03 08:33:38:008 920 1990 AU ## END ## AU: Search for updates [CallId = {ABC7E77F-635F-4192-9B92-CBF9B1CB8AB0} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
2014-02-03 08:33:38:008 920 1990 AU #############
2014-02-03 08:33:38:023 920 153c Misc Microsoft signed: Yes
2014-02-03 08:33:38:023 920 153c Misc Infrastructure signed: Yes
2014-02-03 08:33:38:023 920 153c EP Got 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL: "http://fe1.ws.microsoft.com/w8/2/redir/storeauth.cab"
2014-02-03 08:33:38:023 920 153c Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\117CAB2D-82B1-4B5A-A08C-4D62DBEE7782\wuredir.cab:
2014-02-03 08:33:38:039 920 153c Misc Microsoft signed: Yes
2014-02-03 08:33:38:039 920 153c Misc Infrastructure signed: Yes
2014-02-03 08:33:38:039 920 153c EP Got 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782 redir Client/Server URL: "https://fe2.ws.microsoft.com/v6/ClientWebService/client.asmx"
2014-02-03 08:33:38:055 920 153c PT +++++++++++ PT: Synchronizing server updates +++++++++++
2014-02-03 08:33:38:055 920 153c PT + ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}, Server URL = https://fe2.ws.microsoft.com/v6/ClientWebService/client.asmx
2014-02-03 08:33:38:055 920 153c Agent Reading cached app categories using lifetime 604800 seconds
2014-02-03 08:33:38:055 920 153c Agent Read 0 cached app categories
2014-02-03 08:33:39:211 920 153c Agent * Added update {E7FF661C-6A03-4387-A1EE-1D723B52EF60}.3 to search result
2014-02-03 08:33:39:211 920 153c Agent * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
2014-02-03 08:33:39:211 920 153c Agent * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
2014-02-03 08:33:39:211 920 153c Agent * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
2014-02-03 08:33:39:211 920 153c Agent * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
2014-02-03 08:33:39:211 920 153c Agent * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
2014-02-03 08:33:39:211 920 153c Agent * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
2014-02-03 08:33:39:211 920 153c Agent * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
2014-02-03 08:33:39:211 920 153c Agent * Added update {BFA8C8B8-EEF7-4A82-A36C-8F760F792430}.3 to search result
2014-02-03 08:33:39:211 920 153c Agent * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
2014-02-03 08:33:39:211 920 153c Agent * Added update {A9A0E183-0667-46D6-84E4-17CEBCEE5A22}.1 to search result
2014-02-03 08:33:39:211 920 153c Agent * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
2014-02-03 08:33:39:211 920 153c Agent * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
2014-02-03 08:33:39:211 920 153c Agent * Found 13 updates and 31 categories in search; evaluated appl. rules of 69 out of 94 deployed entities
2014-02-03 08:33:39:211 920 153c Agent *********
2014-02-03 08:33:39:211 920 153c Agent ** END ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03 08:33:39:211 920 153c Agent *************
2014-02-03 08:33:39:211 920 1a64 Report REPORT EVENT: {0786C161-F6DC-4842-85D6-9506124654AD} 2014-02-03 08:33:38:008+0100 1
147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 Windows Update Command Line Success Software Synchronization
Windows Update Client successfully detected 0 updates.
2014-02-03 08:33:39:211 920 1a64 Report REPORT EVENT: {1E5D9728-220F-44A3-8BCC-ADE69687531D} 2014-02-03 08:33:38:008+0100 1
156 [AGENT_STATUS_30] 101 {00000000-0000-0000-0000-000000000000} 0 0 Windows Update Command Line Success Pre-Deployment Check
Reporting client status.
2014-02-03 08:33:39:211 920 1a64 Report REPORT EVENT: {57BAB7D0-685B-4D73-BDF7-82AFCE8675B0} 2014-02-03 08:33:39:211+0100 1
147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 Windows Update Command Line Success Software Synchronization
Windows Update Client successfully detected 13 updates.
2014-02-03 08:33:39:211 920 1a64 Report CWERReporter finishing event handling. (00000000)
2014-02-03 08:33:39:227 920 153c Agent *************
2014-02-03 08:33:39:227 920 153c Agent ** START ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03 08:33:39:227 920 153c Agent *********
2014-02-03 08:33:39:227 920 153c Agent * Online = No; Ignore download priority = No
2014-02-03 08:33:39:227 920 153c Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-02-03 08:33:39:227 920 153c Agent * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-02-03 08:33:39:227 920 153c Agent * Search Scope = {Current User}
2014-02-03 08:33:39:227 920 153c Agent * Caller SID for Applicability: S-1-5-21-4260610346-2664610402-3334891387-1155
2014-02-03 08:33:39:258 920 153c Agent * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
2014-02-03 08:33:39:258 920 153c Agent * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
2014-02-03 08:33:39:258 920 153c Agent * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
2014-02-03 08:33:39:258 920 153c Agent * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
2014-02-03 08:33:39:258 920 153c Agent * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
2014-02-03 08:33:39:258 920 153c Agent * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
2014-02-03 08:33:39:258 920 153c Agent * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
2014-02-03 08:33:39:258 920 153c Agent * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
2014-02-03 08:33:39:258 920 153c Agent * Added update {A9A0E183-0667-46D6-84E4-17CEBCEE5A22}.1 to search result
2014-02-03 08:33:39:258 920 153c Agent * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
2014-02-03 08:33:39:258 920 153c Agent * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
2014-02-03 08:33:39:258 920 153c Agent * Found 11 updates and 29 categories in search; evaluated appl. rules of 58 out of 94 deployed entities
2014-02-03 08:33:39:258 920 153c Agent *********
2014-02-03 08:33:39:258 920 153c Agent ** END ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03 08:33:39:258 920 153c Agent *************
2014-02-03 08:33:39:258 920 153c Agent *************
2014-02-03 08:33:39:258 920 153c Agent ** START ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03 08:33:39:258 920 153c Agent *********
2014-02-03 08:33:39:258 920 153c Agent * Online = No; Ignore download priority = No
2014-02-03 08:33:39:258 920 153c Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-02-03 08:33:39:258 920 153c Agent * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-02-03 08:33:39:258 920 153c Agent * Search Scope = {Current User}
2014-02-03 08:33:39:258 920 153c Agent * Caller SID for Applicability: S-1-5-21-2212025170-3189117132-1219651784-500
2014-02-03 08:33:39:305 920 153c Agent * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
2014-02-03 08:33:39:305 920 153c Agent * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
2014-02-03 08:33:39:305 920 153c Agent * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
2014-02-03 08:33:39:305 920 153c Agent * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
2014-02-03 08:33:39:305 920 153c Agent * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
2014-02-03 08:33:39:305 920 153c Agent * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
2014-02-03 08:33:39:305 920 153c Agent * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
2014-02-03 08:33:39:305 920 153c Agent * Added update {BFA8C8B8-EEF7-4A82-A36C-8F760F792430}.3 to search result
2014-02-03 08:33:39:305 920 153c Agent * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
2014-02-03 08:33:39:305 920 153c Agent * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
2014-02-03 08:33:39:305 920 153c Agent * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
2014-02-03 08:33:39:305 920 153c Agent * Found 11 updates and 30 categories in search; evaluated appl. rules of 60 out of 94 deployed entities
2014-02-03 08:33:39:305 920 153c Agent *********
2014-02-03 08:33:39:305 920 153c Agent ** END ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03 08:33:39:305 920 153c Agent *************
2014-02-03 08:33:39:305 920 153c Agent *************
2014-02-03 08:33:39:305 920 153c Agent ** START ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03 08:33:39:305 920 153c Agent *********
2014-02-03 08:33:39:305 920 153c Agent * Online = No; Ignore download priority = No
2014-02-03 08:33:39:305 920 153c Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-02-03 08:33:39:305 920 153c Agent * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-02-03 08:33:39:305 920 153c Agent * Search Scope = {Current User}
2014-02-03 08:33:39:305 920 153c Agent * Caller SID for Applicability: S-1-5-21-4260610346-2664610402-3334891387-1323
2014-02-03 08:33:39:352 920 153c Agent * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
2014-02-03 08:33:39:352 920 153c Agent * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
2014-02-03 08:33:39:352 920 153c Agent * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
2014-02-03 08:33:39:352 920 153c Agent * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
2014-02-03 08:33:39:352 920 153c Agent * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
2014-02-03 08:33:39:352 920 153c Agent * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
2014-02-03 08:33:39:352 920 153c Agent * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
2014-02-03 08:33:39:352 920 153c Agent * Added update {BFA8C8B8-EEF7-4A82-A36C-8F760F792430}.3 to search result
2014-02-03 08:33:39:352 920 153c Agent * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
2014-02-03 08:33:39:352 920 153c Agent * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
2014-02-03 08:33:39:352 920 153c Agent * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
2014-02-03 08:33:39:352 920 153c Agent * Found 11 updates and 30 categories in search; evaluated appl. rules of 60 out of 94 deployed entities
2014-02-03 08:33:39:352 920 153c Agent *********
2014-02-03 08:33:39:352 920 153c Agent ** END ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03 08:33:39:352 920 153c Agent *************
2014-02-03 08:33:39:352 920 153c Agent *************
2014-02-03 08:33:39:352 920 153c Agent ** START ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03 08:33:39:352 920 153c Agent *********
2014-02-03 08:33:39:352 920 153c Agent * Online = No; Ignore download priority = No
2014-02-03 08:33:39:352 920 153c Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-02-03 08:33:39:352 920 153c Agent * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-02-03 08:33:39:352 920 153c Agent * Search Scope = {Current User}
2014-02-03 08:33:39:352 920 153c Agent * Caller SID for Applicability: S-1-5-21-4260610346-2664610402-3334891387-1282
2014-02-03 08:33:39:383 920 153c Agent * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
2014-02-03 08:33:39:383 920 153c Agent * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
2014-02-03 08:33:39:383 920 153c Agent * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
2014-02-03 08:33:39:383 920 153c Agent * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
2014-02-03 08:33:39:383 920 153c Agent * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
2014-02-03 08:33:39:383 920 153c Agent * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
2014-02-03 08:33:39:383 920 153c Agent * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
2014-02-03 08:33:39:383 920 153c Agent * Added update {BFA8C8B8-EEF7-4A82-A36C-8F760F792430}.3 to search result
2014-02-03 08:33:39:383 920 153c Agent * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
2014-02-03 08:33:39:383 920 153c Agent * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
2014-02-03 08:33:39:383 920 153c Agent * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
2014-02-03 08:33:39:383 920 153c Agent * Found 11 updates and 30 categories in search; evaluated appl. rules of 60 out of 94 deployed entities
2014-02-03 08:33:39:383 920 153c Agent *********
2014-02-03 08:33:39:383 920 153c Agent ** END ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03 08:33:39:383 920 153c Agent *************
2014-02-03 08:33:39:383 920 1990 AU >>## RESUMED ## AU: Search for updates [CallId = {66AF0139-896D-4607-8660-B66D2B58EA26} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
2014-02-03 08:33:39:383 920 1990 AU # 12 updates detected
2014-02-03 08:33:39:383 920 1990 AU #########
2014-02-03 08:33:39:383 920 1990 AU ## END ## AU: Search for updates [CallId = {66AF0139-896D-4607-8660-B66D2B58EA26} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
2014-02-03 08:33:39:383 920 1990 AU #############
2014-02-03 08:33:39:383 920 1990 AU All AU searches complete.
2014-02-03 08:33:39:383 920 1990 AU AU setting next detection timeout to 2014-02-03 10:18:51
2014-02-03 08:33:44:211 920 1a64 Report CWERReporter finishing event handling. (00000000)
2014-02-03 08:41:39:472 920 1a64 EP Got WSUS Client/Server URL: "http://elias:8530/ClientWebService/client.asmx"
2014-02-03 08:41:39:472 920 1a64 PT WARNING: Cached cookie has expired or new PID is available
2014-02-03 08:41:39:472 920 1a64 EP Got WSUS SimpleTargeting URL: "http://elias:8530"
2014-02-03 08:41:39:472 920 1a64 PT Initializing simple targeting cookie, clientId = c5e26849-287b-4b96-ba5d-1489d6fad2f2, target group = , DNS name = dt-ikt-tor.framnes.lan
2014-02-03 08:41:39:472 920 1a64 PT Server URL = http://elias:8530/SimpleAuthWebService/SimpleAuth.asmx
2014-02-03 08:41:39:519 920 1a64 EP Got WSUS Reporting URL: "http://elias:8530/ReportingWebService/ReportingWebService.asmx"
2014-02-03 08:41:39:519 920 1a64 Report Uploading 2 events using cached cookie, reporting URL = http://elias:8530/ReportingWebService/ReportingWebService.asmx
2014-02-03 08:41:39:566 920 1a64 Report Reporter successfully uploaded 2 events.
2014-02-03 08:42:13:212 920 178c Report WARNING: CSerializationHelper:: InitSerialize failed : 0x80070002
2014-02-03 08:43:40:450 920 178c AU ########### AU: Uninitializing Automatic Updates ###########
2014-02-03 08:43:40:450 920 178c WuTask Uninit WU Task Manager
2014-02-03 08:43:40:513 920 178c Service *********
2014-02-03 08:43:40:513 920 178c Service ** END ** Service: Service exit [Exit code = 0x240001]
2014-02-03 08:43:40:513 920 178c Service *************Today I opened Control Panel / Windows Updates and first did a check for new updates (from the WSUS server). Nothing was found and it reported Windows is Updated. Then I clicked the link Check for updates from Microsoft via internet, and
it found around 24 updates.
This is confirmation of the point that I made in the previous post. The updates are *NEEDED* by this system, but the updates were not *AVAILABLE* from the assigned WSUS Server. You were able to get them from Windows Update, but that does not fix your continuing
issue with the WSUS Server.
but it still reported the original 108 Needed updates.
Exactly. As previously noted, the client is functioning perfectly. The problem is NOT with the client; the problem is with the WSUS Server. The updates that this client needed were not AVAILABLE to be downloaded from the WSUS server.
Why this is the case requires further investigation on your part, but is either because the updates are not properly approved, or the update FILES are not yet downloaded from Microsoft to the WSUS server.
It appears that the wsus server doesn't get any information back from the client despite that it displays new Last contact and Last Status report timestamps.
This conclusion is incorrect. The WSUS Server got every bit of information available from the client -- you've confirmed this by the number of updates reported as "Needed" by the Windows Update Agent to the WSUS Server.
I assumed that the log would display if the updates were downloaded or not.
It will log when the updates are actually downloaded. If there's no log entries for updates being downloaded, then they're not being downloaded. If the logfile says "Found 0 updates", then that means exactly what it says: It couldn't find any approved/available
updates to download.
In your case it "Found 11 updates", but now it will be impossible to diagnose that fault, because you went and got them from Windows Update.
All Win8 versions are checked in the WSUS server's Product list so the updates should at least have been downloaded to the server.
This is why understanding the infrastructure is so critical. Your conclusion is invalid based on the premise given, and you may be using improper terminology which only confuses the rest of us as well.
First, selecting updates for synchronization only gets the update metadata (i.e. the detection logic) downloaded to the WSUS database.
The Second Step in this process is to Approve those updates for one or more WSUS Target Groups that contain the appropriate client systems. Following the approval of an update, the WSUS Server downloads the INSTALLATION FILE for that update.
Once the WUAgent sees an approved update and the installation file is available, then the WUAgent will download the file and schedule the update for installation.
Most of the post I read about my problem is about upgrading a 2008 WSUS server to support Win8 / Server 12 clients. When I try to run this update on my Server 12 WSUS it refuses to run (probably because it is for Server 2008).
Yeah.. totally different issue in those posts than what you're describing here.
What should I do to try to track down the problem?
Well.... now that it's 11 days since the logfile was posted, and you've already updated that system, we'll first need to find another system exhibiting the same issue.
Then I'll need to ask a number of questions to properly understand the environment, as well as what you have or have not done.
Then, from there, we can attempt to figure out why your Windows 8 client apparently sees some updates as approved/available but is still not downloading them. We do not yet have sufficient information to even speculate on a possible cause -- there are several.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds. -
WIndows Server 2012 w/ Hyper V and Windows 7
I have been able to create every imaginable virtualization in a test environment except for Windows 7. It asks for drivers. I have a driver CD but when I put the CD in the D: drive. It will run but suddenly the command line screen states that a file on
the F: drive does not exist. Where is this F: drive coming from?I might have misstated my situation. I have Windows Server 2012 outfitted with Hyper-V. I'm trying to virtualize a Windows 7 operating system.
I found a another W7 media disk that seems to bypass this problem. -
Hyper-V Host Server 2012 R2 x64 drive c:
All VMs, including SBS 2011 Standard x64 are on drive d:
I replaced my motherboard and defined a Marvell RAID 1 Mirror for my boot drive C:. My drive D: containing all of my Hyper V machines remained untouched since the new MB had Intel Matrix Controller with RAID 5, as did the old MB.
Since the C: drives are a few bytes smaller after configured as a RAID 1, I was unable to restore drive C from the image copy, so I rebuilt a new Hyper-V Host identical as possible using Server 2012 R2 x64. I had to redefine the Hyper-V machines on
the host, and the 1st time I brought it all (host and VMs) I had to reconfigure the NICs due to new MAC addresses, and verifying SBS 2011 DNS and DHCP for all physical and Hyper-V machines. Otherwise my Hyper-V SBS 2011 x(64) wasn't touched.
Now the SBS Exchange 2010 is not receiving mail. In the Exchange Management Console clicking on the Organization config gives me a highlighted error "You don't have sufficient permissions to view this data". The Server
Config is no longer on the EMC. The Recipient Config looks fine.
Outlook 2013 x64 connects to the Exchange Server, but no new mail appeared. There were just a few older messages that came in since the last time I opened Outlook. My public DNS on GoDaddy was not changed. I did not change sending mail
through my ISP Sonic.net. The SBS internal DNS doesn't have an MX record, but I'm not sure it ever did since my GoDaddy public DNS has an MX record.
I tried restoring to an earlier Image Copy, but that made no difference. I'm using the Windows Backup from SBS 2011 for my daily image copy backups.
- Michael FaklisHi Michael,
à
After more research and running the Best Practices report from the EMC, I am missing a slew of ManagementRolesAndRoleGroups from the RBAC container.
Based on your description, it seems that you have find the cause of this issue. On current situation, I still
suggest that you should run
SBS 2011 BPA and then check if can find some relevant errors. Just for a confirmation.
Meanwhile, please refer to following articles and check if can help you.
Apply
missing Exchange 2010 RBAC Management Roles and Policies
RBAC Manager
(Exchange 2010 SP2)
Hope this helps.
Best regards,
Justin Gu
Maybe you are looking for
-
Can not restart Microsoft SharePoint Foundation Web Application after stopping
All, thanks for any help. I have a SP2010 instance running and am in the process of adding custom web parts, activities, and timer jobs. As part of troubleshooting an odd problem where my code did not seem to be getting updated on deployments, I dec
-
Updated from Firefox version 3.5.7 and it won't run. I get this error - it say's XULRunner Error: Platform version '1.9.2.3' is not compatible with Minversion>= 1.9.2.11 Maxversion>= 1.9.2.11
-
I'm trying to parse XML being returned from a service but having no luck. I've written a unit test to parse a sample that looks like this: *<?xml version="1.0" encoding="UTF-8"?>* *<ShoppingLists xmlns="http://service.mydomain.com/2011/01" xmlns:i="h
-
SQL Loader control file script - INFILE
Hi, The data stored in the file "c:/test_<yyyy>_<mm>_<dd>". The <yyyy>, <mm> and <dd> has to be from sysdate. The infile gets generated on daily basis. LOAD DATA INFILE 'c:/test_'||to_char(sysdate,'yyyy')||'_'||to_char(sysdate,'mm')||'_'||to_char(sys
-
How to Connect Form 6i to MS.SQL 7.0, urgent !
dear all, I am new in Form 6i. Can anyone tell me, how i can access to MS. SQL 7.0 from Form 6i. Can I logon to multiple database (Oracle & SQL) ? How ? Thank You. null