anyweb

it's a good question, where i'm currently at is in the midst of being ugpraded from SMS to SCCM, and with that getting SUP implemented, OSD, windows 7 and so on, there are 6 or so sms/sccm admins managing (i'm one) doing various tasks such as application packaging,dsitribution, troubleshooting, patch management, and so on, the task are split up because the company is global so there always has to be something done somewhere, i'm dealing with the server upgrade, SUP implementation, and OSD (windows xp > windows 7), i sometimes do packaging too cheers niall

ok can you post the SMSTS.log file here please

you obviously removed more than you needed, as the error means as follows: 12 USMT_FAILED_MIGSTARTUP (Error in XML file ‘Bad XML’) so take another look at your xml's and check for typos etc cheers niall

R3 Beta Released! Configuration Manager 2007 R3 Beta has been released! As a member of the Configuration Manager 2007 R3 Open Beta program you can download at this Connection via the downloads tab. https://connect.microsoft.com/

if you need to add IIS and other server type roles then MDT integration will make it easy (for server roles and features), otherwise you'll have to script it all.

and di you check diskpart as i asked above ?

you can build, customise as much as you want, and then capture as a separate task sequence, here's how http://www.windows-noob.com/forums/index.php?/topic/1543-how-can-i-capture-windows-7/

the recommended way is by using unattend.xml, i've given a short example of that here

is the firewall on the server ?

no, do this while the computer is logged on in windows, in the RAP (run advertised programs) select your Capture task sequence it will apply the autologin, remove from domain, reboot, prepare configmgr, and capture the os

do you have the possiblity of doing remote desktop, i can rdp in if you want ?

well then you stagger the deployments by shifting the collection target (in the deployment management task(s)) or using maintenance windows i'd suggest to test both ways imagine this scenario i set a maintenance windows of every thursday at 3pm - 5pm and i have some new updates for xp boxes, i advertise those new updates via a deployment management task and i set the deadline to one minute from now.. on thursday between 3pm - 5pm (during the maintenance window) the updates get installed to that specific collection you can have multiple maintenance window collections or multiple patch collections that you can stagger the software updates installation to.. see what i mean ?

ok then you'll have to tell me more about your lab/setup then, because something is not configured correctly... have you tried pushing the client again, watching it install in task manager processes (ccmsetup.exe) and then seeing if it lists the site code ? is client push configured like so ? http://www.windows-noob.com/forums/index.php?/topic/491-how-can-i-configure-sccm-2007-sp1-in-windows-server-2008/

if you log on as a user with local admin privs on that box, do you see any change in behaviour ?

what tickbox ? if you remove 'ignore main....' then the updates should only install during the maintenance window

what discovery methods have you setup/configured ? what does your ccm.log say on the client ? what does the mpcontrol.log

why use a script, thats what maintenance windows are for, have you looked into using maintenace windows on collections yet ?

well create the deadline as one minutes ahead of when you are creating the deployment management task to speed it up a bit

the regedit happens on the CLIENT not on the SERVER,it allows us to autologin so that we can reboot/capture... the autologin package will do this automagically

is the firewall enabled on the win7 client ? are your boundaries correctly configured ?

easy, just add the autologin package *its explained in the post* and adjust the task sequence so that it uses YOUR boot image

have a read of the following http://technet.microsoft.com/en-us/library/bb632393.aspx Hide all deployments from end users

http://blogs.technet.com/systemcenter/archive/2010/04/20/video-recap-of-mms-so-far.aspx and from the Video, here are some highlights:- an update to MDT 2010 will be released (most likely Sp1 based on Modena), R3 beta is mentioned !! and that's all about Power Management in Configmgr 2007 "we are very excited to release the R3 beta !!" the screenshot below is from the video and its the Power Management tab on a collection in SCCM 2007 R3. The next screenshot shows Enviromental reports in R3 and below is a screenshot of vNEXT, the next version of ConfigMgr, note that the old MMC interface is gone Focus Points: 1. User Centric Client Management In the past ConfigMgr has been pushing out stuff to computers (machine) but now they are going to become more User Centric, pushing out the right application to the right user at the right time in the right format. 2. Simplification of the Product Designed for Large distributed networks and is complex and hard to administer and install. So the focus is to make wizards better, pre flight checks, clear and concise logging, simplifying the process, simplifying the back end server replication, sender capable distribution points with scheduling built in to reduce server workload. 3. Improving whats there Auto Approval of updates, think of Updating antvirus updates 4 times an hour, with auto update it can be simplified and improved. Watch the rest of the video here http://blogs.technet.com/systemcenter/archive/2010/04/20/video-recap-of-mms-so-far.aspx

ok how about click on a computer in a collection, right click and choose Distribute, Software... then go through the wizard, is that what you wanted ?

some screenshots and the actual errors in your site status would be useful, you can attach those logs if you want