Peter33

I had this problem only once after a console crash, but this is what helped me. Look in the comments section how te edit the SQL table.

Hi, we got a little issue with an WSUS update today. The server team published the update for the Windows Management Framework 3.0 on all servers. Unfortunately that was causing the MP Control Manager to fail on all SCCM Servers . The mpcontrol.log showed some WMI errors. So i looked which updates lately got installed and found the KB2506143 in the list. The solution was to uninstall KB2506143, reboot the server and hide the update. After that i just had to remove the management point roles and to reinstall them. Here is someone with the same issue. The Microsoft answer is sorta funny.

Yep, our current TS takes lie 60-90 minutes depending on the chosen options. Unfortunately. I'm counting the days until SP1

Hi Tech, since you are using MDT already put your HTA in the script folder of it. Also after the "use toolkit package" run a gather step (for later use to collect the local data; make your TS dynamic). Then call your HTA with %ToolRoot%\ServiceUI.exe -process:tsprogressui.exe %SYSTEMROOT%\system32\mshta.exe %SCRIPTROOT%\my.hta This will also hide the task sequnce progress as long as the HTA runs.

Hi light, this flag is for the build and capture of an image to prevent windows to show the activation dialog after the deployment of the final image. There should be no harm though to use it. I guess your are running a KMS server for the activation.

If your are talking about OSD, yes applications apply very slow, because the task sequence policies will be compiled before the execution of every single application. This is addressed to be fixed with SP1.

Well, that explains the reboot. The Windows Installer receives the exit code 3010 (soft reboot) from the installation and initiates the reboot. With a normal package/application Installation this would be a pending reboot. Unfortunately the beviour in task sequnces is different. In your SCCM logs you will just see an "unexpected reboot". The good new is that you can avoid this by using a script wrapper which replace the exit dodes 3010 and 1641 (hard reboot) simply with a 0. The bad news is that your following installation of JRE will fail until the computer got restarted due to blocked files in the program files folder. I am using a powershell script as normal application for the whole process. At first it checks if any java application is running and skips the installation if java is used. otherwise it uninstalls all outdated Java Runtimes with a WMI query. As next step it checks again if any java version is installed and only installs the new version if no other installation is present. Otherwise it will force an error as exit code. Finally it will install our company certificates. The application is applied to a dynamic collection which checks the installed java version of the clients (all clients without the latest version).

Are you doing this in a task sequence?

You can use UTC instead of local times for your deployments, but no other specific time zone.

Site Database Server is a standard role for Secondary Servers and will be installed automatically when you set up a new Secondary Site. You can't remove it.

How did you configure the network card of your VM? It should be set to bridged networking. Can you resolve the server name and is the IP adress covered by a boundary? Is the system time on your machines in sync? You need only the vmware drivers for network and storage from the vmware tools.

Sounds a bit strange. That never happened to me before. You might just recreate the boot wim, or double check that you applied the correct PE to your task sequence. If you have applied several optional task sequences to the same collection and boot your client with PXE, the PXE server will load a "random" PE out of these sequnces. In this case you have to apply a "reboot to assigned PE" as mandatory first step in your task sequence, to make sure the correct one will be used. Just by the way. You are not trying to build and capture a 64 bit windows 7 with a 32 bit PE? Because that would not work at all.

You usually don't need drivers for hyperv. Check the smsts.log for a detailed error description.

OK, that sux. But i would rather chain 2 different applications then, to get a decent exit code from the office installation. So just create a new application only holding the script/batch for creating the shortcuts, and make it dependant to the office application.

Hi light, yes, tha`t's a run command line somewehere after Setup Windows and ConfigMgr, but before enabling bitlocker (in case you do in your task sequence).

Not that i have tried it yet. But how about "[ProgramFilesFolder]\Microsoft Office" ? That should be readable for the installer. http://msdn.microsof...1(v=vs.85).aspx If someone could try this and give a feedback? We will migrate next year to Office 2013.

Hi lightiv, keep in mind that you will need the BDE partition if you plan to use Bitlocker on Windows 7 Enterprise Laptops. So think about the MDT step i mentioned. As a side note. Deactivate the "client rapair on boot" on your Windows 7 machines (bcdedit /set {default} bootstatuspolicy ignoreallfailures) right in your task sequence. As soon as a client repair triggers, the client will be unable to log on to your domain.

For SCCM these clients are "unknown". So you don't have to worry about that. Just add the "all unknown computers" collection to your OSD collection.

He has no partitioning step in his task sequence. If you use MDT you can easily create the BDE Partition by adding 3 new steps after the apply OS step. - use toolkit package - gather - run command line (cscript.exe "%ScriptRoot%\ZTIBde.wsf" /debug:TRUE) This will create a new BDE partition if none exists. It also applies the boot manager and makes it the boot partition.

Hi Rocket, the hight cpu usage was obviously caused by the SP1 for SQL 2012 together with SCCM2012 SP1. That was just a test setup. It was kinda strange. Everything was working, but unbelievable slow. SQL was permanently using at least 80% of the processor time. The rest was used by the .NET optimization. The smsexec got alomost nothing. So working with the console was like clicking on something and then go for a coffee. Mabybe the final SP1 for SCCM2012 will also support SQL2012 SP1. At the moment my home lab is also runnning with SQL 2012 CU3 without any problems. The cpu usage only raises slightly when the WSUS synch runs.

LOL, nice trap. I'm pretty sure that will help out several people some time when playing around in lab environments. A working DHCP/DNS configuration is a must.

Forget about the data image then. If it's really the BDE partition it's not needed. Windows will apply the correct files for the BDE partiton itself. if the partition exists on your machine. Just by the way. The correct partition would be be Disk 0 Partition 0.

What's the data image good for? Seems you didn't specify a valid drive for the image to apply to. There are no more volumes available for use. The requested target could not be resolved to a valid volume on this computer. Check your task sequence to ensure this drive is correct and that it is being created

I would not use SP1 for SQL 2012. This is not a supported configuration. But you need to install at least CU2, better CU3. I tried that in a VM for testing reasons, and it turned the SQL server (only together with SCCM2012) into some kind of CPU hog. The machine was permanently running at 100% cpu usage, even after limiting the server to one core. You don't have CPU usage proplems with this configuration?

Make sure that your boundaries are configured correctly. Obviously these clients are in a subnet that is not covered by a published sccm site.