anyweb

Microsoft has released the second Service Pack for Windows Server Update Services (WSUS) 3.0, tailoring the solution to the latest iteration of the Windows client and server platform. As of August 25th, 2009, customers having deployed WSUS in their environments can download Windows Server Update Services 3.0 SP2. WSUS is a server solution set up to streamline the delivery of updates from Microsoft Update to corporate environments. With WSUS 3.0 SP2 RTM, Microsoft delivers a variety of management, stability, reliability and performance enhancements, revealing that it has integrated customer feedback into the service pack. In addition, SP2 brings to the table new features and fixes for bugs discovered since the previous release. official wsus blog > http://blogs.technet.com/wsus/ Operating Systems Supported by WSUS 3.0 SP2 Server · Windows Server 2008 R2 · Windows Server 2008 SP1 or later · Windows Server 2003 SP1 or later Client · Windows 7 client · Windows Server 2008 R2 · Windows Server 2008 SP1 or later · Windows Server 2003 SP2 or later · Windows Vista · Windows XP Professional · Windows XP Professional SP1 · Windows XP Professional SP2 · Windows XP Professional SP3 or later · Windows 2000 SP4 For more information about WSUS 3.0 SP2 including documentation and download instructions, see: 1. Windows Server Update Services 3.0 SP2 Dynamic Installer for Server Manager (KB972493) 2. Windows Server Update Services 3.0 SP2 (KB972455) Additional information For more information about this release visit us at our Windows Server Update Services page. The Product Team would like to thank you for your support throughout Beta and RC of this release. Thank you for making WSUS a better product! Download it here

well i don't know ifit will work but we'll do our best to try and get it working, i know we managed to get sccm working with an nt4 DHCP server so I can't see why solaris won't work

welcome to the forums and to SCCM 2007 you'll need sp2 beta for sccm if you want to deploy windows 7 or windows server 2008 R2, you can separate your installation servers into two separate servers, one doing AD, DNS and the other doing SCCM and SQL and WDS (and optionally MDT) what operating system is your DHCP server running ? good luck

if you are just testing sccm then using the eval is fine, but for production use you must use the full product

try this one collection Name = AD Security Group Member and Adobe Reader 8.1.3 NOT installed Query select SYS.ResourceID,SYS.ResourceType,SYS.Name,SYS.SMSUniqueIdentifier,SYS.ResourceDomainORWorkgroup,SYS.Client from SMS_R_System as sys where sys.ResourceId not in (SELECT ARP.ResourceID FROM SMS_G_System_ADD_REMOVE_PROGRAMS AS ARP WHERE ARP.DisplayName = "Adobe Reader 8.1.3" AND ARP.Version = "8.1.3") and sys.SystemGroupName = "sccm2007\\Adobe Reader Users" The above query will show all members of an active directory group called Adobe Reader Users who do NOT have Adobe Reader 8.1.3 obviously change the query to suit your domain/ad sec group and program name/version

Microsoft has confirmed that upgrade editions of Windows 7 will be available in Europe when the new operating system launches on October 22. The company had previously said that only full version would be on offer. The initial limitation of a full, clean-install only edition was part of the plans... more > http://www.neowin.net/news/main/09/08/24/windows-7-in-europe-full-upgrade-and-family-pack-editions

with XP deployments its normally ALWAYS the sata mode in bios, so change it from AHCI to ATA and reboot and try again

Please note that this guide is designed to get you Deploying Windows 7 with SCCM in a LAB Environment as quickly as possible. This guide is provided as is, if you find any errors please report them in the forums. In a production environment please consult Technet for best practise, see below links: Operating System Deployment: Determine Your Operating System Deployment Method Operating System Deployment in Configuration Manager Overview of Operating System Deployment Configuration: System Center Configuration Manager 2007 Best Practices: Configuring Configuration Manager Sites for Best Performance Checklist for Security Best Practices Best Practices for Central and Primary Site Hardware and Software Configuration Best Practices for Operating System Deployment Step by Step 4 part guide to Deploying Windows 7 Enterprise. Deploy Windows 7 part 1. Build and Capture Part 1 is the longest part of the 4 part guide and covers the steps required to successfully Build and Capture Windows 7 RTM. It was tested successfully on both X86 and X64 Enterprise RTM releases. Step 1. get the ISO Step 2. Add Operating System Install Package Step 3. Create Distribution Point for the Image Step 4. Update Distribution Point Step 5. Create the Build and Capture Task Sequence Step 6. Advertise the Build and Capture Task Sequence Step 7. Add a system to the Build and Capture 7 collection Step 8. PXE boot the newly added Windows 7 client Deploy Windows 7 part 2. Add the captured WIM file Step 1. Add the Captured Wim file as an Operating System Image Step 2. Distribute the Captured WIM file Deploy Windows 7 part 3. Create a new Task Sequence Step 1. Create a new Task Sequence Deploy Windows 7 part 4. Advertise the Task Sequence Step 1. Advertise the Task Sequence Step 2. Last Actions enjoy ! cheers

look at my post above yours

hyperv works fine, my second lab runs exclusively on hyperv and that is one AD server (2008) one SCCM server (2008), one Server 2008 R2, 2 xp and 2 windows 7 clients curently and i too didn't have to add anything to the boot images, all the machines aside from AD and SCCM were deployed via the sccm server in hyperv so, we'll need to see your log files to understand what you problems really are, or are you forgetting to Add a Legacy Network card and adding it as first boot device ?

are you deploying XP or what ??? and on what type of hardware

indeed, and the guide actually points that out too i've now re-worded it to say 'local administrative' to make it clearer and included a link back to here so others can see what happens cheers niall

no, you need the full release version

i just did a quick test on a win7 virtual client here and using a user that is a member of local administrators on the windows 7 pc i could remote desktop client to it via SCCM, all systems collection, right click, choose Start, Remote Desktop Client and it worked just fine, no UAC prompts at all. And this is on a clean install of windows 7 with no gp's applied aside from 1. enable remote desktop 2. disable firewall the os was Windows 7 Enterprise X86 (32bit)

its on Technet and MSDN

don't use the UPGRADE dvd, use the FULL release version available from MSDN or TECHNET or your Volume License download page

ok then good verify that the ConfigMgr DVD that you are using is the correct one from Technet and not the Upgrade version.

is this server a member of an AD ?

ok then on one of the clients that is not showing up as approved, as Peter requested can you post thos two logs here

you say only 4 out of 20 are showing in the console, do you mean that they are all showing up in the console but only 4 show as 'approved' ? or `?

ok should be fixed now, time was wrong on the server

are you seeing the wrong time in posts or somewhere else ?

Step 1. Advertise the Task Sequence In the Operating System Deployment node, click on Task Sequences and right click on the Task Sequence we just created, choose Advertise when the General screen comes up, choose the settings as below in the screenshot, you can browse to a collection called Deploy 7 (you should have created this collection beforehand). Schedule Set your schedule depending on whether you are in a Lab or Production Environment. For a Lab Environment Make the Task Sequence mandatory by clicking on the yellow star and select As soon as possible. Select ignore maintenance windows when runing program and allow system restart, set the program rerun behaviour to always rerun program so that we can rerun the task sequence over and over as we require for testing. For a Production Environment In a Production environment set the advertisement from Mandatory to Optional, this gives us less risk of an accidental deployment but also introduces the possibilty of choice. if you want to remove choice then keep the advertisement mandatory but change the program rerun behaviour to never rerun (see below screenshot). select the following Distribution Point options show the task sequence progress and click next, next, next and close. at this point you can right click on the Deploy 7 collection, choose properties and you'll see our new Task Sequence is advertised to that collection Step 2. Last Actions All you have to do now is Add systems to the Deploy 7 collection and pxe boot them, then they will get imaged with our pre-captured Deploy 7 Enterprise X64 RTM image. You can do this in many ways, either by Direct Membership, Computer Association, AD groups membership.... job done !

Step 2. Distribute the Captured WIM file Expand Operating System Images and then Expand our newly added Windows 7 Enterprise RTM Release node right click on Distribution Points and click on New Distribution Points as this is NOT a boot image only select the first DP for Copy Package click next and close Right click on Distribution Points again and this time choose Update Distribution Points, click Yes when prompted Next Step, Create a New Task Sequence