anyweb

yeah, this is one of those funny errors, i should make a Tee-shirt out of it :-)

The supported versions of SQL Server 2008 and SQL Server 2008 R2 are listed here on Technet:- http://technet.micro...nfigSQLDBconfig SQL Server 2012 is not yet supported, when it is it'll be added to that list. cheers niall

are you sure the updates are on your distribution points ? how many updates are deployed to your build and capture windows 7 X64 collection ?

computername and mac is fine, you can have GUID plus ComputerName or MAC plus ComputerName or a combination of all three

client push requires a lot of behind the scenes to work properly, if using auto client push then firewalls and local admin account access are needed amongst other things. on the server side check ccm.log (as Peter said) on the client side look at ccmsetup.log or if client installation fails client.msi.log if nothing happens on the client then verify that the firewall is allowing traffic through from the configmgr server, and that the client push installation account is a member of the local admin group

computers that need updates which you make available to your organization are not compliant, computers that have all available updates installed are compliant, speaking of compliance, if you want to see what updates a computer needs then you could drill through the software update compliance reports and work out what it needs, but be prepared to take your time..

spread the word !

take a look at Planning for Sites and Hierarchies in Configuration Manager here on Technet first. Then, if you decide against a standalone primary setup (which can have secondaries and dp's) you can read my hierarchy setup guide here to further understand the do's and don'ts.

if you want to upgrade ConfigMgr 2007 then you have to use the side-by-side approach as I explain in this post. using Configuration Manager 2012 RC in a LAB - Part 14. Performing a side-by-side Migration from Configuration Manager 2007 Part 14. Performing a side-by-side Migration from Configuration Manager 2007. [January 27th, 2012]

there is Cu6, look at my using System Center 2012 Configuration Manager - Part 1. Installation - CAS Part 1.Installation - CAS the download link is there

CU6 is listed as the supported install version now

D:\ is just a suggestion, you can put it wherever you want, but seeing as most people frequently run out of space on C:\ due to poor planning i'd suggest another drive letter other than C:\, also SQL is IO intensive (disk read/write) and if possible you should try and install on it's own hard disc. Also you don't want to mix SQL or other programs (Configuration Manager) with the operating system, think about performance ..

well in my example above SMSadmin is the user running the configmgr console and that user is a local administrator of the same box, are you performing this as a user that has local administrative permissions on that server or has the user rights to read/write to that folder (the package source folder mentioned in your log file)

the build and capture method is definetly recommended as its 100% automated, the method above requires manual steps, but achieves the same result

good stuff, so for everyone else i'll explain the solution, create a Configmgr client Package (from definition) and use that package for the setup windows and configmgr step and not the built in one, otherwise you cannot change from 'download' to 'access' cheers niall

which configmgr client are you using in the task sequence ? the built in one, or one you created yourself (from a package from definition) ? if you use the build in package then you cannot change it's properties, instead, create a new one from 'create package from definition' and then make the appropriate changes to that package and use that pacakge in your task sequence

i would definetly upgrade to CU6, stop all CCM releated services then do the upgrade, reboot

When you install new computers it would be nice to be able to easily name the computer as part of the deployment, otherwise the new computer could end up with a name like MININT-XRGHJTF unless you import it into Configuration Manager first. You can script around this in your task sequence or use web services or HTA's but the easiest method of all is to set a Collection variable called OSDComputerName. This method does not require any scripting all you need to do is to Enable Unknown Computer support in the Distribution Point PXE tab settings. To prompt the end user to enter a computer name In Configuration Manager 2012 by using the OSDComputerName variable you first need to think about the computers you are aiming this at, and in this case the computers are unknown computers, that is, they are unknown to Configuration Manager. Step 1. add the collection variable Now that we know that they are unknown we need to select the Unknown Computers collection called All Unknown Computers. Right click and choose Properties. select the Collection Variables tab and click on the Yellow star burst button as shown below enter the following variable name when prompted OSDComputerName, remove the checkmark from Do Not Display this value in the Configuration Manager console as in the screenshot below click ok and apply so that it looks like this Step 2. Make sure you have Deployed a task sequence to the Unknown Computers collection Verify that you have deployed your chosen task sequence to the Unknown Computers collection by selecting the task sequence and clicking on the Deployments tab. The deployments listed should include one for the All Unknown Computers collection as shown below. If not, then create a new deployment for the task sequence and choose the All Unknown Computers collection for that deployment. Step 3. PXE boot a new computer PXE boot a new computer. Press F12 when prompted Note: make sure the computer is NOT present in Configuration Manager prior to this, either as a previous computername or as an UNKNOWN object, if it is, highlight it in All Systems and delete it. select your task sequence and click next now you will see a Task Sequence window called Edit Task Sequence Variables double click on OSDComputerName, the following should appear type in a computername click ok and the computername value should be listed to the right of the variable name as shown below click next and the task sequence completes as normal Step 4. Verify that it worked Now that the Task Sequence is complete you can logon to your computer, bring up the computer properties and note the computername is what you entered earlier. the variable is set during the Apply Windows settings step of the task sequence and you can see the collection variable being added in the SMSTS.log file (found in C:\Windows\CCM\Logs) that's it, I told you it was easy ! cheers niall

what exact version of SQL server did you install ? when running the SPLASH.HTA are you logged in as a domain user or as local administrator ?

check what antimalware policy is listed on the client

what accounts are the sql services running as ? are you running sql server 2008 r2 sp1 cu6 ?

not following you, what are you trying to migrate from and to ?

using a domain admin account for the SMSAdmin user would be a huge security risk and is definetly not best practice, create the SMSadmin user using any username you wish (SMSadmin is easy to remember..) and the user should just be a regular domain user, adding them as local administrator on the configuration manager server(s) is sufficient for our needs. the other accounts listed as used to get the job done, test users are for testing things, domjoin for joining the domain during OSD

please read this post and hotifx KB article http://www.windows-noob.com/forums/index.php?/topic/3718-adding-a-hotfix-to-the-setup-windows-and-configmgr-step-in-a-task-sequence/

what does your smsts.log file say, have you applied the kb2509007.. hotfix ? http://www.windows-noob.com/forums/index.php?/topic/3718-adding-a-hotfix-to-the-setup-windows-and-configmgr-step-in-a-task-sequence/