anyweb

This post isn’t directly related to Operations Manager, but I thought it might be useful to those running lab environments and looking for ways to optimize their hardware resources. Windows 2008 Core is one way to reduce the footprint of the OS hosting your virtualized servers. When I decided to move my VM’s to Hyper-V hosted on Windows 2008 Core, I went through some pains which led me to create this document outlining these procedures for later use. This should save you some time and effort when you decide to go ’hardcore’. This walk-through assumes a clean installation of Windows Server 2008 Core, with no roles yet installed. Note: Text throughout this document that has a red font indicates a variable you need to provide. Ensure your hardware supports Hyper-V First ensure the latest BIOS have been installed. Boot into BIOS and enable “Hardware Assisted Virtualization” and “Hardware Enforced DEP”. Verbiage may not be exactly as quoted here, depending on your hardware, but should look similar. If these settings are not found in BIOS, Hyper-V is not supported on that system. This is usually because either the processor is not capable of supporting Hyper-V or the Mainboard cannot support Hyper-V. Check for required hotfix to support Hyper-V WMIC QFE List should reveal KB950050. If not, download and install. Note: Windows Server 2008 with Service Pack 2 includes this hotfix. KB950050 is not listed if SP2 is installed. Example: KB950050 is not listed. KB955430 indicates SP2 is installed. image Set Time Zone Control TimeDate.cpl Example: Control TimeDate.cpl image Note: Regional settings are configurable during installation. If this needs to be changed after installation for some reason, the Date Time applet can be launched using this command. Rename Computer NETDOM RenameComputer %ComputerName% /NewName:ComputerName Note: It’s not necessary to restart until after you have joined the computer to the domain in a later step. Configure Network Interfaces NETSH Int IPv4 Show Int Note the “Idx” of the interface which you’ll be updating. This is any network interface that is connected to the LAN. Example: Output displays which interface to note. clip_image002 NETSH Int IPv4 Set Address Name=”5” Source=Static Address=xxx.xxx.xxx.xxx Mask=xxx.xxx.xxx.xxx Gateway=xxx.xxx.xxx.xxx NETSH Int IPv4 Add DNSServer Name=”5” Address=xxx.xxx.xxx.xxx Index=1 NETSH Int IPv4 Add DNSServer Name=”5” Address=xxx.xxx.xxx.xxx Index=2 Note: Index is the DNS search order. It is not necessary to configure more than one DNS server. Product Key Activation I added product key activation steps, but you may skip this section if you’ve already activated or do not wish to activate now. Install the product key: SLMGR /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx Activate the product key: SLMGR /ato Join to domain It is not required for the server hosting the Hyper-V Role to be a member of a domain. Having the client running the Hyper-V Manager tool in the same domain as the server running the Hyper-V Role reduce some configuration options, but workgroup or otherwise disjoined servers will work as well. If you do not wish to join the Hyper-V server to a domain, you may skip this step. NETDOM Join %computername% /Domain:domain /Userd:username /Passwordd:* /SecurePasswordPrompt /REBoot:seconds Install and Start Hyper-V Set Hyper-V to auto-start: BCDEDIT /Set HyperVisorLaunchType Auto Install Hyper-V Role: Start /w OCSetup Microsoft-Hyper-V Configuring Hyper-V Download and install the Hyper-V Management Tool. Vista download (requires Vista SP1+): http://support.microsoft.com/kb/952627 Download the HVRemote tool (http://code.msdn.microsoft.com/HVRemote). Unpack the VBScript (HVRemote.wsf) to a location accessible by the server hosting the Hyper-V Role and the workstation you will be using to run Hyper-V Manager. Alternatively, copy it to a location on the local machine(s). On the server hosting the Hyper-V Role HVRemote.wsf /add:domain\user Note: If this is not a domain joined machine, just add the local administrator account or another account of your choosing as follows. HVRemote.wsf /add:computername\Administrator On the client that will be used to manage Hyper-V (running Hyper-V Manager) HVRemote /mmc:enable Connect to Hyper-V host Open Hyper-V Manager on the client, right-click on the top node “Hyper-V Manager”, and select Connect to Server… Additional configuration steps If your Hyper-V host and the client running the Hyper-V Manager are not in the same domain, there may be additional configuration steps required to connect to the host. If you’re unable to connect to Hyper-V host in previous step, try these additional configuration steps in the order listed, and attempt to connect to Hyper-V host in Hyper-V Manager after completing each step. First try If the client running Hyper-V Manager and the server hosting the Hyper-V Role are not in the same domain, or are running workgroup mode, you may need to add the server credentials to Local clients CredSSP store. cmdkey /add:hyper-v_hostname /user:hyper-v_hostname\user /pass:password Second try Open REGEDIT and navigate to the following key: HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefault If you do not see a key hierarchy as follows… clip_image004 …save the registry editor text below to a *.reg file and import these keys. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults] "DebugLogLevel"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowDefaultCredentials] "Hyper-V"="Microsoft Virtual Console Service/*" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowDefaultCredentialsDomain] "Hyper-V"="Microsoft Virtual Console Service/*" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowFreshCredentials] "Hyper-V"="Microsoft Virtual Console Service/*" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowFreshCredentialsDomain] "Hyper-V"="Microsoft Virtual Console Service/*" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowFreshCredentialsWhenNTLMOnly] "Hyper-V"="Microsoft Virtual Console Service/*" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowFreshCredentialsWhenNTLMOnlyDomain] "Hyper-V"="Microsoft Virtual Console Service/*" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowSavedCredentials] "Hyper-V"="Microsoft Virtual Console Service/*" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowSavedCredentialsDomain] "Hyper-V"="Microsoft Virtual Console Service/*" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowSavedCredentialsWhenNTLMOnly] "Hyper-V"="Microsoft Virtual Console Service/*" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\PolicyDefaults] [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\PolicyDefaults\AllowDefaultCredentials] "Hyper-V"="Microsoft Virtual Console Service/*" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\PolicyDefaults\AllowDefaultCredentialsDomain] "Hyper-V"="Microsoft Virtual Console Service/*" Third try In most cases, the previous steps should allow you to connect to the Hyper-V host. In some cases, anonymous access to DCOM may need been to be explicitly granted. This can be accomplished with the HVRemote program as follows. HVRemote /AnonDCOM:grant Windows Server 2003 Virtual Machines in Hyper-V Network Adapter Caveat Windows Server 2003 requires SP2 in order to install the Hyper-V Integration Services. 1. Create ISO of SP2 and “Insert Disk” for installation. Apply Service Pack 2 to any virtual machines running Windows Server 2003. 2. After SP2 has been applied, “Insert Integration Services Disk” and the Network Adapter drivers will be detected. * 0 Comments read the full post with screenshots here > http://blogs.technet.com/b/jonathanalmquist/archive/2010/10/10/install-and-configure-hyper-v-on-windows-2008-core.aspx

did you create your USMT 4 packages ? is this an mdt task sequence ? more details please

then perhaps you have other issues with that computer such as WMI, have you tried repairing wmi ?

This month’s batch of security patches from Microsoft will be a record-breaking one: 16 bulletins addressing a whopping 49 security vulnerabilities. According to the company’s advance notice, four of the 16 bulletins will be rated “critical,” Microsoft’s highest severity rating. Microsoft rates a critical vulnerability as one that could be exploited to propagate an Internet worm without user action. The 49 vulnerabilities will mark the largest ever batch of patches issued by Microsoft. The previous record was 34 vulnerabilities patched in August this year. The October patch batch will include fixes for security flaws in the Windows operating system, the Internet Explorer browser, Microsoft Office and the .NET Framework. It is very likely that Microsoft will include patches for a pair of elevation of privilege vulnerabilities that were exploited during the mysterious Stuxnet worm attack. The flaws in this month’s release affect all version of Windows, including the newest Windows 7 and Windows Server 2008. via > http://www.zdnet.com/blog/security/ms-planning-patch-tuesday-whopper-16-bulletins-49-vulnerabilities/7433?tag=content;feature-roto

just as Peter says, if you follow the Deploy Server 2008 guide it'll show you how to do just that, cheers niall

if it's not detected by configmgr then it won't work with it, i don't recall reading any support for USB 3.0 devices with configmgr, i would guess that is coming in R3 or if not, in vNext cheers niall

good work, is it functioning correctly now ?

add the computer to a collection that you are advertising office 2007 to, and make that collection membership based on a query which is an Active Directory security group membership

i'm sure people would love to read how you did it all, so feel free to share the info

I just wanted to post a quick note to say how happy I am to have received a 2010 Microsoft® MVP Award (SCCM), it was a very pleasant surprise as I read the email on my phone while stuck in traffic on my way home from work. I want to thank a few people for guiding me on the right path, in particular Aidan Finn for his superb advice and support, to Jason Sandys for his guidance and support and to the following in no particular order, Rod Trent (http://www.myitforum.com), Kent Agerlund, Ronni Pedersen, Michael Petersen, Stefan Schorling, Peter Van Der Woude and the rest of the great folks at windows-noob.com !! I also owe a great deal to my family for their patience and understanding while I worked towards this goal, the long nights and countless hours are paying off, and I'm going to make it up to you !! and last but not least, Microsoft, for giving me the award !!!! and giving us SCCM. thanks ! cheers niall

Internet Explorer 9 Beta made its debut earlier this month and was met with warm reception by our customers and partners. As we have talked about previously, one of the ways we measure success for IE is through customers choosing our latest product offerings. This month that means we get to expand our usage share conversation to include IE9 Beta. Net Applications’ browser usage share report released today shows IE9 Beta usage share at 0.25% for the two weeks after launch. The tech enthusiast community is observing a notable increase in IE9 activity: LiveSide reported IE9 Beta users accounted for 25% of their reader base, IE9 overtook IE6 users at DownloadSquad, and Network World reported poll results showing 47% of people intend to try IE9 Beta. Additionally, we saw tweets from the likes of Ed Bott who noticed, “Halfway through Day 1 of IE9 availability, 8% of my ZDNet visitors are using the beta. Steady increase all day, higher than IE7.” Over the past few months we’ve discussed Internet Explorer 8’s prominence worldwide. Following earlier trends, IE8 continued its growth this month, making our browser usage share growth 0.57% for our current offerings (IE8 and IE9) in September. We are pleased to report that customers are choosing more modern browsers, as evident by the continued decline of IE6 and IE7 usage (drops of 0.63% and 0.50% respectively in September according to Net Applications). This is goodness for the industry as a whole. Two weeks after IE9 Beta launch, we continue to see great reactions from our customers. As of today, IE9 Beta has been downloaded 6 million times, which is two and half times what we saw with IE8 Beta in a similar timeframe. Plus, a great many users are researching and testing the new features in IE9 with over 30 million page views to the Beauty of the Web site. We look forward to seeing more and more people enjoy a beautiful web with IE9. Ryan Gavin Senior Director, Internet Explorer Business and Marketing via > http://windowsteamblog.com/ie/b/ie/archive/2010/10/01/ie9-beta-momentum-in-september-6-million-downloads.aspx?utm_source=windows-noob.com

no nothing is wrong, when you upgrade to SP2 then you have to rebuild any custom boot images, the boot images in your screenshot are the new versions that can support Windows 7 and Windows Server 2008 R2, if you are not using a custom boot image then do nothing further apart from verify that your task sequences reference the new boot images and that they are distributed to your dp's

well you could target the machine with a task sequence that just restores the user state and make it mandatory, p.s. my name is Niall not andy

is there cisco switches involved ? if so is portfast set to enabled or disabled ?

nice to hear it and hope you link back to here in whatever document/seminar/etc you release and it's great to see you Citrix guys here !

you can use one task sequence to do this but it does require running on both systems, obviously, plus the logic behind it will probably need some work, however you can start with a standard task sequence and work from there once the computer association is in place

what do you mean it didnt work ? did you update the collection membership/refresh ?

yes of course you can remove the client browse to the ccm installation folder on the pc (your path may be different depening on OS and ARchitecture) open a command prompt, browse to C:\Windows\ccmsetup and enter the following ccmsetup.exe /uninstall wait 5 minutes and refresh the control panel you should see the icons are gone cheers niall

try the following Query instead, notice the use of = instead of like All Windows 7 systems select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from sms_r_system where OperatingSystemNameandVersion = '%Workstation 6.1%' All Windows Vista Systems select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.OperatingSystemNameandVersion = "%Workstation 6%"

youll need the Quest plugin, you can get it from here

what reg key are you trying to add/edit ? and how ? are the systems 64 bit ?

it should be possible, what have you tried so far ?

try disabling your firewall and then run the site discovery again, does it work ? also try to repair the install by clicking on Repair in the components tab

just after a client is installed and before it get's it's policies from the configmgr server, it will appear like you say, with just two actions, under the advanced tab if you click on Discover what happens ? additionally you can initiate the two actions that are present and about 5 minutes later watch to see if the client actions tab gets the new policies (refresh your view/f5)

first of all why are you trying to remove the client ? what is wrong with having it installed ?