Rocket Man

Have seen this error on all my SCCM implementations, I totally ignored it and forgot all about it, until now BUT everything is working as it should on all SCCM locations, if this helps!

In most setups that I have done to date I create a sources folder as per the guide here on W-Noob. This would be the same as your Storage folder I gather?? I only ever share this out to my network access account(co-owner) and that is it, no-one else, because I personally feel no-one else needs to have permissions to browse the contents of it other than this account. (NO need for NTFS permissions, just simply share it out!!) You have configured your software distribution account AKA as network access account?? And you have made the SCCM site server's computer account a member of the local administrators on the server? If you have done all of these then I would suggest creating a temporay share on the root of your drive called Sources for example and share it out to your network access account. place your application in here and re-create your application, do the configurations, distribute to the DP(s), and then deploy it to a system or user collection. If this works then you know it is something to do with your security on the Storage directory! Rocket Man

Happy New Year Fellow Noobs, may it be a great year for everyone! :D Rocket Man

A SQL server instance is needed for Windows ADK?? (not too sure about this) The 1st instance(default) will be MSSQLSERVER in a SQL setup. To check which collation you have configured your DB engine with follow these simple instructions: http://msdn.microsof...y/hh230914.aspx If it is not SQL_Latin1_General_CP1_CI_AS then you can follow this guide to change the collation: http://andysal.wordp...server-2008-r2/ I had a similar problem when I tried installing SCCM 2012 on Server 2012 and SQL BI 2012(testing environment...not supported). I did run the above command and it did change the collation but SCCM pre-reqs failed continuously. I changed the SQL edition to Enterprise with CU2 and it worked seemlessly!! Which edition are you using and have you installed any SQL CU for SQL 2012?

Why do you need to convert it to MSI? You can use any executable file and still deploy it using the application model, once you have the the correct silent switches for it.

Also make the site server a local admin on itself! This is needed if you are deploying a remote DP so i would assume you would have to the same on a standalone site server hosting a DP!

Yeah I had a similar question and it seems to be an area that is going to have to be achieved to suit your own needs through trial and error!! http://www.windows-n...onthly-updates/ You could try and put in a filter when creating the ADRs like Expired(NO) and superseded(NO) along with the product. You may have to change the setting on your SUP to never expire updates also, again I am not too sure on this. Rocket

SP1 RTM is soon available: http://myitforum.com/myitforumwp/2012/12/13/its-official-sc-2012-sp1-has-rtmd/ http://www.windows-noob.com/forums/index.php?/topic/6864-report-after-adr/

Hi Hoping someone can advice on this. I currently have 20 DPs and one Primary Site with a DP also. I have just setup a SMP on the Primary Site Server. In the set up it asks for a path to the store location. This has to be drive path. Is it possible to enable a SMP on all my remote DPs. My initial thoughts were YES, but because of not been able to add a UNC path to the store folder how will this work? Can it work? It is working at present as I am after migrating some small data from a remote machine back to the SMP on the central server, but if this data was quite large, say 5GB, well I would not want this centrally captured to the store and again restored back across the WAN links. Any suggestions? Thanks Rocket Man

Hi is the RTM SP1 Garth EDIT: http://myitforum.com/myitforumwp/2012/12/13/its-official-sc-2012-sp1-has-rtmd/ YES it is

Which method of OSD are you deploying, PXE or Staging? Will it not install even via staging?(running the TS out to it while in a live OS environment) Well if you have done it correctly it should atleast show the out of box x86 unknown object and x64!! You are selecting all systems before searching I assume? Have you tried unknown PXE on it by deleting this sytem's object out of the SCCM DB and deploying the TS to the unknown computer collection? You could get the systems MAC address whilst it's in PXE mode or through the CLI and there is a report in the reports somewhere that you can identify a MAC address to a machine name.....it may have a duplicate!!! Rocket

Any unknown entities if you search all systems for unknown? Is the client on this machine?

Have you checked the BIOS clock on the machine to see if it is correct? Is there a duplicate entry in the console for this machine? Rocket Man

Did you add SMSMP=sccmserver.fqdn to the properties of the configMgr properties in the TS. Also are you building and capturing a physical machine??

Can I ask why you are installing drivers in a Build & Capture? Are you using a VM for this process? I would not apply drivers at a build and capture TS, I would only apply drivers on a build TS. You should try just a build and capture without drivers in any way. Then with the captured image create a new TS and then apply your driver package with WMI query!! It is a waste of an image the way you are trying at moment due to the fact if it was successful with the drivers, then you would only be able to deploy this build & capture image with drivers out to the same model of machine.........if you try and deploy it out to different model then you could get errors including maybe BSOD due to driver incompatibility due to the fact the drivers are hardcoded in the image..... This is the beauty of WMI queries and driver packages......you can basically use a standard image without any modifications and deploy it to any model, aslong as you have the appropriate driver packages attached with WMI queries to suit (and this can be as many as you like on the one TS). Rocket

Hi Are you running a Build & Capture??

Without been rude...You still have not answered the initial question........do the current systems in the SCCM console in the all systems collection currently have the site code? It does not matter if they have or have not the client installed, they should still have the site code!! If not then this in an indication that your boundary is not correct!! As for the configMgr client from defintion I would be fairly sure it is recommened, make sure to tick the box to distribute to the content share in the properties of the new package! Rocket Man

Does it stop at the driver package at OSD time or bypass it swiftly? What is your WMI query syntax? Neither have I used SCCM for XP........as you know it is a different sysprep process. I am fairly sure there is a section here on the Windows Noob site that covers XP, it may be in the SCCM 2007 guides! Rocket Man

OK but do your current systems(after doing system discovery of AD) in all systems collection have the site code regardless if they have the client or not? For your OSD you did create a new configmgr client from definition and distribute to DP and use this as your configmgr setup task in your TS?

Well if it is a single domain then of course it will be able to authenticate at any of the other sites, but your Group Policy is site specific not unless you are using the default domain policy at root level, then this will filter through to all sites instead of having GPOs on OUs' etc..

p Do any of your existing systems in the SCCM console have the ADX site code yet. The client does not need to be installed for this, well this is on a green field site not sure about a migration. If they dont then it may be an indication that your boundary is not right..

It should be there, it is on my test SP1 site....maybe you have to do an initial sync of FEP or something else and it may update the product catalog.. Office 2013 is not on mine but i'd be sure it will be soon with RTM.

This is an optional update, just checked my servers as I do not allow SCCM to manage them and I also have auto updates turned off, they download but I choose what to install(some extra management but worth it in cases like this). I have now made this update hidden on all Site servers. Also my win 7 ADRs' on all sites have 3 filters associated with them Bulletin ID(MS), product(windows7) and superseded(NO). This update was filtered out due to the Bulletin ID filter(thankfully). It is in the all software updates group but it shows not downloaded and my ADR is running tomorrow a week later after patch tuesday, this is not a mistake, I do this for cases like this also, the ADR runs tomorrow and the deadline is 2 days after this each month so i have 9 days of a windows to catch problematic updates if they arise. Thanks peter.

Disable the default apply driver task that comes with the creation of the task sequence and add the new driver package task with WMI query in or around the same location after apply OS but definitely before setup configuration manager client task!