lord_hydrax

I would remove the information regarding the WSUS server from Group Policy. I think you should only disable Windows Updates from being configured in Group Policy and let SCCM configure/control the update settings. Having a WSUS server specified in Group Policy might confuse the client.

To stop the distribution point from being available you could remove it from the boundary group temporarily.

Ohh I see, alright thank you.

I was injecting some new updates into our Windows 7 wim file today and I noticed it is sitting at 6.4GB these days. Not really sure what options are around for compressing these files. I did a bit of a google and it looks like DISM in the Windows 8 AIK has some compression options, such as this: Dism /Export-Image /SourceImageFile:C:\install.wim /SourceIndex:1 /DestinationImageFile:C:\sources\install.wim /DestinationName:"Windows 8 Pro" /Compress:Maximum Will that work with Windows 7 or is there a better way?

We have collections for DEV, IT, UAT and Production to spilt out the phases for Workstations. Only recently started using ADR's for deploying to DEV and IT which has been going well. Hoping to automate the whole process soon. Also I do get the ADRs to create a new group each month, as it is handy for reporting.

At what stage are you getting this error? I often see our IT Support staff get this error if UEFI is left on in the BIOS. Since we don't support UEFI yet, we have to turn it off in the BIOS before we can deploy an image. http://abortpxe.wordpress.com/2014/04/16/failed-to-run-task-sequence-0x80004005/

Are you running SCCM 2012 SP1 and the Windows 8 ADK? You need these to have the required boot images for deploying UEFI as far as I am aware. In any case, there is a stack of information about deploying with UEFI on this page that should help: http://www.windows-noob.com/forums/index.php?/topic/6250-how-can-i-deploy-windows-8-in-uefi-mode-using-configuration-manager-2012/

Thanks for confirming!

Ahhh I don't think I am even running R2 yet, might have to give it a bit more thought now.

If you create a new computer account in AD first there is no MAC or GUID information when the computer is later 'discovered' by SCCM and imported. Or if there is, it is something randomly generated because AD will not know the correct information from the machine for manually created AD accounts. And of course SCCM needs that information to link to available deployments advertised to a machine. Perhaps if you created the AD Account and also manually imported the computer information into SCCM they might sync together and get your desired outcome. I'd be kinda surprised if that would actually work though. I'd say you need to find a different means to get the software installed, perhaps import the computer into SCCM and after applying to image and joining to the domain, add the computer to the software groups and have the software install outside of the TS.

You tried removing the Client package off the DPs and redistributing them? And monitor say the smsdpprov.log on the DPs to ensure they are copied over without issue.

Any updates on this? We've just come across the Fixed Drive USB issue ourselves.... such a pain. We had Kingston DataTraveler 100 G3 USBs that were working fine then in a later revision of the device they made them Fixed USBs for Windows 8. Damn you Microsoft!

In this article Rocket Man actually has a script for prompting for computer name if you check the comments: http://www.windows-noob.com/forums/index.php?/topic/5542-how-can-i-easily-prompt-for-a-computer-name-in-configuration-manager-2012/ I had a look for the prompt for computer name script I have and its actually that one mentioned. If you want to go down the path of HTA, it takes a bit of configuration and testing to get it right and I'd suggest doing a bit of research beforehand. I had help from a number of different articles on the web before I got it right for our systems.

I haven't done that exactly, but all you need to do is create a new collection and instead of a query rule use a INCLUDE rule and select the all systems collection. Make sure it is scoped to the all systems collection as well of course. What we do in our environment, is we have a collection setup purely for PC refreshes and add computers to it as required. This is so users do not inadvertently boot into WinPE and generate a helpdesk call wondering wtf is going on. With your script question btw, yes there are a few scripts around to set the computer name in the task sequence. I used to use a HTA frontend to do computer name, location and software but it got a bit annoying to manage so I just went with a couple of basic collection variables for now.

Your Task Sequence is deployed to at least two collections, the Unknown Computers collection and maybe All Systems Collection (for PC refreshes as you described). If you browse to the Task Sequence in the SCCM Console, you will see where else it is deployed in the Deployments Tab that comes up at the bottom. You need to define the OSDCOMPUTERNAME variable on whatever the other collection is so it will prompt. You can't however define variables on the default All Systems collection if that is what you are using. (You could in CM07 I believe, but not CM12) The work around if you want to do that is to create a collection that includes all the members of the All Systems collection and deploy the TS there as well as set the collection variables there.

You can configure applications to run a scripted installer rather than an MSI. So if you create say a powershell script to copy/install the module, you can use that as the application.

The method I suggested would require 12 deployments (1 for each collection of servers) to be created. This can be done at any time, so you could create the 12 deployments at the start of the quarter and just stagger the installation deadlines for them over 12 weeks as you desire. Alternatively you could create each one a week before the intended deadline or whatever, its up to you.

It sounds like you are using different Deployment Types, look into using dependencies instead. I too got caught on this one. Dependencies can be found in the properties of a deployment type. I would say what you are trying to achieve is completely possible though. Create seperate applications for both MSIs, have one MSI be a dependency of the other one. If 'APP1' is a dependency of 'APP2', deploy 'APP2' to deploy both MSIs. Create two applications, one with the script and one with the Office 2013 package. Make Office 2013 a dependency for the Script. Deploy the script. Also, in the Application Catalog tab of the Scripts Properties, you can give it a nice name that makes it look like you are just installing Office.

You could tackle it a bit of a different way, by setting up 12 device collections with the servers required in each one. Then create one quarterly software update group with all the updates and deploy that to each of the 12 collections as required. Thus you ensure you have the same updates through the whole process.

You can hide/delete the folder from the 'all users' start menu folder in this location: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft System Center 2012\Configuration Manager\Software Center.lnk

I've seen a lot of SQL queries over the years for finding missing Task Sequence packages on a Distribution Point, and never got one to work. All I wanted to do was query a server name and a task sequence package ID to find out what applications or packages referenced by the TS still need to be distributed. I finally actually got one to work (SQL isn't my strongest area ) so I thought I'd share with everyone: SELECT DISTINCT TSR.PackageID ,PS.PackageID ,PSD.Name FROM v_TaskSequencePackageReferences AS TSR JOIN v_PackageStatus AS PS ON TSR.RefPackageID = PS.PackageID JOIN v_PackageStatusDetailSumm AS PSD ON TSR.RefPackageID = PSD.PackageID WHERE TSR.PackageID = '<TSPACKAGEID>' AND PS.PackageID NOT IN (SELECT PS.PackageID FROM v_PackageStatus AS PS JOIN v_TaskSequencePackageReferences AS TSR ON PS.PackageID = TSR.RefPackageID WHERE PS.PkgServer LIKE '%<SERVERNAME>%') Replace <TSPACKAGEID> with the Task Sequence's unique Package ID and <SERVERNAME> with the hostname of the Distribution Point you want to query. Also anyone who is familar with the 'Create Task Sequence Media' wizard, you can use that to check what servers are missing packages as you get a listing of servers and the number of packages from the TS that it has. Good starting point to find DPs that have missing packages.

I think those WMI entries are created after installing the SCCM Client. Maybe there is a problem with the client package for this computer? Otherwise it points to a corrupt WMI repository, and you might need to add a step before installing software to clean or rebuild it.

For my vbs packages I just have the commandline vbscript.vbs and that works ok on its own. Try running it without cscript.exe at the start and see if there is any difference.

Looks like the Management Point is not installed at all, it keeps failing with a fatal error when it tries to install. I think this article is relevant to do a clean install of a MP and worth a shot: http://social.technet.microsoft.com/Forums/systemcenter/en-US/adb67f6a-8c57-4f8b-8651-af97fa76219c/sccm-management-point-installation-errors?forum=configmgrbackup - Remove the MP as a site system role (if it is still installed), wait for it to finish - Remove IIS completely - Reboot the server - Stop the Task Scheduler Service - Rename the %windir%\Tasks folder to something else (or move it) - Start the Task Scheduler Service (this will recreate the %windir%\Tasks folder) - Reinstall IIS, BITS, WebDAV - Ensure BITS and WebDAV are enabled - Reinstall the MP