Iroqouiz

Place a file on all drives where you don't wish packages to be stored, called NO_SMS_ON_DRIVE.SMS It could be an empty txt file, just make sure it's named exactly like I wrote. The file extension must be .SMS This should really be done before installing SCCM, but if you place the file there now you should be good to go.

What does the AIUpdateSvc.log file on the server say?

The log file indicates it can't find a drive to save information on. I've gotten these error messages a few times, for 2-3 different reasons. 1. The disk is corrupted (quick solution=create a new VM and test, have had to do this multiple times in the past) 2. The disk is not partitioned correctly at the beginning of the TS. Solution that works great for me is this: create a txt file and call it diskpart.txt. Paste the following in the txt file SELECT DISK 0 CLEAN CREATE PARTITION PRIMARY SELECT PARTITION 1 ACTIVE mount the boot images you use in your TS:s with DISM and copy diskpart.txt to Deploy\Scripts At the beginning of your TS, this has to be the first step, add a Run Command Line step and call it Pre Stage Disk. This should be the command line: diskpart.exe /s "X:\Deploy\Scripts\diskpart.txt" *Important information* This step can ruin information if the physical computer has more than one disk connected. You should disconnect all drives and just leave the intended OS disk.

Have you checked the client installation log files? Are you sure they've been installed successfully? It doesn't seem like it.

I still have this issue sometimes, no idea what triggers it. It always boots up to the correct boot image though, so it doesn't seem to matter ultimately. Just annoying.

Do you use Google Translate? It's very difficult to understand what you're trying to say.

Hey, This solved the problem for me. I had some SCOrch IPs installed. http://support.microsoft.com/kb/2800707

I've made a collection that picks up all unknown clients. When re-imaging computer over and over in a lab, you get quite a lot of those and I find it's easiest to collect them all in the same spot. Then I can mass delete.

Yeah, apply that hotfix first of all. And then make sure your SMSadmin account has permissions to save the capture in the destination folder, it's not the NAA that does the capture. Also make sure the password is typed correctly. When you set the capture account, did you press Verify after?

Had the same issue sometimes after upgrading to SP1. I have to say, SP1 doesn't really seem suited for upgrading, too many weird things happened to my site. I've set up a new server (Win Srv 2012, SQL 2012) and installed SP1 from scratch and I haven't seen any of these or other issues so far, knock on wood. I'm preparing to migrate all the clients soon.

I had the same issue when upgrading to SP1 RTM. Rreinstalling DP/MP did not help. I actually started setting up a new SCCM server and installing SP1 from scratch. Works fine now. Our environment isn't that big so it didn't take as long as for others I'm sure.

1. I'm not sure, but I think you have to be real picky with how you type the task sequence variables. I would type OSDComputerName instead of OSDComputername. Otherwise it looks good, I use the exact same way to set the computer name in my TS. 2. I would like to see how the settings tab looks, what TS variable you're setting here. Have you tried specifying the DefaultGateway001 variable there? I think that would work.

To clarify, you don't need to delete the app itself, just delete the deployment of it and create a new one

Can you post a screenshot of your TS and also upload the msi log file of the client installation.

SP1 doesn't use WAIK anymore when creating boot images, it uses ADK which you can download if you google a bit.

That technet article never mentions uninstalling WAIK before installing ADK. Was I supposed to do that? My server behaves very strangley after upgrading to SP1 also, it's very sluggish. I get all kinds of errors in the Site Status and Component Status nodes. Last night I rebooted the server so it could install Windows updates, and when I logged in again the Component Status node contained only a few components, like 4-5. I got errors like these I think basically every component or site system role has been in Warning or Critical status a few times since upgrading. Installing applications during OSD sometimes fails also, with different error messages. Apps can sometimes not even be downloaded. I know I'm not being very specific or providing log files, but I can just _feel_ that something's wrong with the server. Was I supposed to create a new ConfigMgr client package and distribute to the DP when I upgraded to SP1? Or was it enough to just update the package on the DP? I should add that everything, apart from WSUS, looks totally fine on server right now. I did a site reset last night. OSD is still kind of shaky though.

Yeah, the RTM console was already installed and when I upgraded SCCM to SP1 and installed the new console, I got the above errors

SP1 was released last week.

Dunno, it was on my license site when I logged in. Think it's called "System Center 2012 Configuration Manager Client Mgmt License with SP1"

EDIT: *SOLUTION IN MY LAST POST* Hi, After upgrading my prod environment to 2012 SP1 everything works great apart from starting the console on my Windows 8 machine. There were no issues with this before when I ran SCCM 2012 RTM or CU2. The console just crashes. Looking in the event log I find this: .NET Runtime crash Application: Microsoft.ConfigurationManagement.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.Reflection.TargetInvocationException Stack: at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[]) at System.Delegate.DynamicInvokeImpl(System.Object[]) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Windows.Threading.DispatcherOperation.Invoke() at System.Windows.Threading.Dispatcher.ProcessQueue() at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame) at System.Windows.Threading.Dispatcher.Run() at System.Windows.Application.RunDispatcher(System.Object) at System.Windows.Application.RunInternal(System.Windows.Window) at System.Windows.Application.Run(System.Windows.Window) at Microsoft.EnterpriseManagement.ConsoleFramework.ConsoleApplication.LaunchWindow() at Microsoft.EnterpriseManagement.ConsoleFramework.ConsoleApplication.Run() at Microsoft.ConfigurationManagement.AdminConsole.Program.Main() and then the SCCM console crash message Faulting application name: Microsoft.ConfigurationManagement.exe, version: 5.0.7804.1000, time stamp: 0x50adcdf1 Faulting module name: KERNELBASE.dll, version: 6.2.9200.16451, time stamp: 0x50988950 Exception code: 0xe0434352 Fault offset: 0x00014b32 Faulting process id: 0x157c Faulting application start time: 0x01cdea5cd70dba7b Faulting application path: C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin\Microsoft.ConfigurationManagement.exe Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll Report Id: 1671ea23-5650-11e2-be86-1803733d64f6 Faulting package full name: Faulting package-relative application ID: I've re-installed the console a few times and rebooted the machine. Obviously .NET crashes the console, but since .NET 4 and 4.5 is included in Windows 8 I can't run the full .NET setup and repair the installation. It says it's already included with the operating system when I run the setup. I've tried turning off all versions of .NET in the "Turn Windows Features on and off" section in the Control Panel, but that doesn't help. The console works fine on Windows 7 and on my SCCM server. What to do?

Released now!

I've tweaked my UDI TS quite a bit, but as I understand it the default TS should be pretty much good to go. You don't have to create several TS, what you choose in terms of refresh/replace/new is then carried through in the TS by task sequence variables.

Thanks a lot

Hi, Why are admins not allowed to install SP1 in a prod environment until GA?

It's working just fine, thank you very much for the help