Jorgen Nilsson

Hi, The beta download at Microsoft.com is a complete installation so you don't have to install the RTM version first and you shouldn't either. http://www.microsoft.com/en-us/download/details.aspx?id=34607 The biggest difference though is that you have to install the Automated Installation kit for Windows 8 manually before installing SCCM 2012 sp1. Regards, Jörgen

No, Only some workarounds that would involve editing the database directly which is not supported and it will not work anyway... The solution would be to delegate permissions to those admins needing permissions to do it to the Central site.. Regards, jörgen

Hi, If you assign the package to DP's from the Central site that is the expected behaviour. If you need to be able to update content e.t.c from a primary site you must assign the content to the DP at the Primary site. regards, Jörgen

Hi, You should have a look at creating a Prestage media task sequence instead, then you will get the WIM file in there as well. Regards, Jörgen

Hi, The client cannot find a boundary from the AD that it is assigned to and if you run ccmsetup.exe without any switches the computer must be within a boundary. Assigning the Site Code via GPo only works when installing the ccmsetup.msi using a group policy. Regards, Jörgen

Hi, If applicaitons are to be visible in the Application Catalog they will have to be deployed as "available" to Users, so if you target Device Collections with you deployments it will not be visible in the Applicaiton catalog. Regards, Jörgen

Hi, Can you please provide some more information, if your question is if you can install a Secondary Site on a Server 2012 server in SCCM 2012 Sp1 the answer is yes. Regards, Jörgen

Hi, If you delete the update package you delete the updates downloaded with it as well as they are downloaded to the Source path you have specified for the Software Update Package. regards, Jörgen

Hi, No, I think you are correct, it cannot be changed or viewed in the console. I would suggest you have a look in either ruleengine.log or patchdownloader.log and see if it is visible there. regards, Jörgen

Hi, It will connect directly to the computer that you want to remote control. Regards, Jörgen

Hi, the client will select an active NIC with an IP Address, the errors in your log file indicates that the client don't have any connection to the Distribution point, if you press F8 and have the command prompt enabled in the boot-images, do you get an IP Addres for the NIC connected via cable? Regards, Jörgen

Hi, You should delete the membership of the collection, if you right click and select delete on the computer it will be deleted from the SCCM 2012 database as Niall wrote. If you deleted the computer you can either start it again it will register automatically again or as you wrote treat it as a "Unknown computer" and reinstall it using a deployment to the unknown computers collection. regards, Jörgen

Hi, there is no way to configure the default behaviour of the application wizard, it will always be selected as standard, you would have to use a script to change it if you don't want to do it manually or script the application creation. Regards, Jörgen

No You can only see in the Status Messages who modified a collection, not exaclty what was changed. Regards, Jörgen

Hi, Option 1: Create a Collection used for OS Deployment and advertise the Task Sequence to that Collection, put the client computer in the collection and reinstall it. Use a script something like this perhaps to remove the computer from the collection after a Succesful OSD. http://ccmexec.com/2012/07/remove-from-collection-and-clear-pxe-flag-vbscript-using-status-filter-rule/ Option 2: Make an optional advertisement to all computers and set a requirement that it can only be run on an OS you don't have in your environment. That way the clients will not execute the TS within Windows but when you PXE boot a computer you can press F8 to boot to SCCM and reinstall the computer as the requirements are not evaluated during PXE boot. Regards, Jörgen

Hi, When you just swap the image the unattend.xml file used isn't changed so I would add a new "apply image" step instead then it should work.. Of course if you have the correct drivers. Regards, Jörgen

Hi, Are you using a sequence of names or is it specific names? if you want to generate them randomly: http://www.deploymentresearch.com/Blog/tabid/62/EntryId/24/Generate-Computernames-in-MDT-2010-based-on-prefix-and-a-sequencenumber.aspx is a great solution for MDT. I use this alot, yes it is a powershell script but it is really straight forward to use:http://ccmexec.com/2010/10/import-computers-into-mdt/ I hope that helps Regards, Jörgen

Hi, Is it deleted from the SCCM Database as well? Should it have the client installed? If it should have the client install install the client and it will register itself in the SCCM console. You can also use AD System Discovery to get it back into the database so that you can deploy the SCCM client to it. Then you will have to add it back to any custom collections used. Regards, Jörgen

Hi, Here is a complete list of hotfixes for SCCM 2007: http://ccmexec.com/configuration-manager-2007-sp2-hotfix-list/ Regards, Jörgen

Hi, If you enable F8 prompt and use it to partition and format the disk before you start the task sequence, does that help? Regards, Jörgen

Hi, have you included any new SATA driver for the new model? Regards, Jörgen

Hi, It sounds like you are updating to many collection with to short update interval so that your server can't handle the load. Or you could have a poorly written SQL query that takes to long time to execute, you can troubleshoot collection refresh problems using the Colleval.log file. Regards, Jörgen

Hi, I woiuld push a new driver to the client as that will probably be a better solution long-term.. You can either uninstall the driver using the command line used to install it perhaps or use Devcon to update the driver depending on platform. Regards, Jörgen

Hi, Here is how such a query could look like.. http://tompopov.blogspot.se/2009/12/dynamic-collections.html Regards, Jörgen

Hi, The toolkit files includes all the files needed from the Deploymentshare or as normally in MDT is used from the Deploymentshare, so basically it enables all the scripts, all the steps in the MDT Task sequence options that exist, without the MDT Toolkit package neither of this will work. You can use a user-Driven (UDI) task sequence where the user is in control of the deployment, where all the files needed are in the toolkit package. So to be able to use the MDT intergration at all in SCCM you need a Toolkit package. Regard,s Jörgen