Quantcast
Channel: Configuration Manager 2012 - Operating System Deployment forum
Viewing all 9126 articles
Browse latest View live

sms-executive-service-crashes in SMP server - SCCM 2012

$
0
0

Hi,

We are using SCCM 2012 for OS migration. We have multiple SMPs based on the location. SMS_Executive service is keeps crashing on one of SMP server even after restart. i have verifed USMT folder and found below things,

1. Folders in the data directory is 129 items and folders in the delta directory (under the Migration Status folder) is 151 items

USMT\SMPSTOREe_0257E7A4$ - 129 items

\USMT\SMPSTOREe_0257E7A4$\MigrationStatus - 151 items


Do need to delete extra folders under "\USMT\SMPSTOREe_0257E7A4$\MigrationStatus" to resolve SMS_Executive service crashing issue? Can you please suggest me


OSD Application Install; OU Requirement

$
0
0

I'm seeing some issues when using an OU (and child OUs) as a requirement for application deployment during OSD.

The target machine logs the application as "not required" during the Task Sequence, I'm guessing because SCCM hasn't got the OU information for the machine, yet. Is there any way I can trigger population of this data in ConfigMgr during OSD to facilitate this requirement specification.

I have a 'workaround' where I read the OU from ADDS however this won't work for IBCM clients - so I end up either having a working TS and breaking IBCM deployment of the applications, or vice versa.

Thanks,

Chris


MCTS 70-640 | MCTS 70-642 | Prince2 Practitioner| ITIL Foundation v3 | http://www.cb-net.co.uk

Operating System Image VS Operating System Installer - what does everyone recommend and which is quicker?

$
0
0

I have worked out that all of the configuration in our windows 7 image can be applied through the task sequence after the operating system is installed. Currently we apply and image and then add configuration.

I am wondering would I be better off just adding a Windows 7 installer instead of imaging? Which method would be quicker?

Would be interested to see how everyone does this.

One thing to consider is windows updates, as if we have an image (WIM file) we can inject updates to it through software update point on patch Tuesday to save having to apply them through the task sequence. We can't inject updates into the installer so time taken to install 100 odd patches has to be taken into consideration.


failed to deploy image from pxe using sccm2012

$
0
0

Hi

After i finish to configure my sccm 2012 environment for operation system deployment

and  i finish to upload all data (boot images,operations system images)to my distribution point and deploy the task sequenes

when i try to boot  the computer with  PXE i get this error "pxe-m0f exiting pxe rom " "selected boot device failed. press any key to reboot the system"

i try to troubleshoot  this problem with this guide

  • Disable PXE / wait until WDS is uninstalled
  • Remove boot images
  • Delete C:\Windows\Temp\*.*
  • Reboot
  • Delete D:\RemoteInstall
  • Reboot
  • Add PXE support on the DP (WDS install automatically)
  • Reboot
  • Distribute boot images again
  • Restart WDS

but i still get this error

Distinguishing between similar model when installing drivers

$
0
0

I have been succesfully deploying various Dell Optiplex models for the last couple of years.

I'm about to introduce a new model, but the new model has a name similar to the previous models I used.

Here's an example:
Dell Optiplex 9020    (Previous model)
Dell Optiplex 9020M  (New model)

So, in my TS, I use the following:
SELECT * FROM Win32_ComputerSystem WHERE Model LIKE "%Optiplex 9020%"

This has worked great for my previous models, but as we can see, it will not work in my new scenario, because this query will pass for both the "Dell Optiplex 9020" and the "Dell Optiplex 9020M"

Should I make the query more exact (like the following)?
SELECT * FROM Win32_ComputerSystem WHERE Model IS "Optiplex 9020"
SELECT * FROM Win32_ComputerSystem WHERE Model IS "Optiplex 9020M"

or is there another query that would be better to use?

Disk 1 not initialized

$
0
0

Hello

I have created a Task Sequence for my environment, this TS formats Disk 0 and 1. And applies The OS image to Disk 0 and the Data image to Disk 1. The TS applied the images successful and then the client reboots. After the reboot the Disk 1 is not longer initialized.

Somebody seen this before?

Client : Server 2012R2

Greetings


Deploying 100% of available software updates during a task sequence

$
0
0

Hi,

Can somebody tell me if it actually possible to fully patch a computer via an SCCM 2012 task sequence using the install software updates task? If you have managed this can you shed some light on where I'm going wrong? For me, this behaviour is exactly the same as ConfigMgr07... It simply doesn't work as it should.

I've integrated IE9 into my image and then added in all available updates via offline servicing. My task sequence installs windows, installs Adobe Reader, Office 2010 and Visio Viewer 2010. I then reboot the machine and perform all my patching via the Install Software Updates task (with it set to 'all'), then reboot again. I do this four times in total.

It downloads and installs some 24 updates in the first instance. The second, third and fourth time it doesn't download or install anything.

When the task sequence completes and the OS first starts up there are 10 updates waiting to be installed (including updates for Adobe Reader and Flash that I have published to the WSUS server via SCUP). After installing those and rebooting there is a single hotfix available (KB2533552). After installing that and rebooting, .NET4 Client Profile is waiting for me. After that there another nine more updates are available (mainly .NET4). Reboot, .NET4 Framework, reboot 5x .NET4 framework updates.

Why does the software update task not install 'all' updates when that is what I've selected? I have an automatic deployment rule targeted to my OSD and Unknown Computers collections. The rule is set to include Windows 7, Office 2010 and Adobe products with all update classification types.

Status Filter Message OSD deployment

$
0
0

Hello, 

I have created a Task Sequence that is used in multiple one-way trusted domains. 

One of the requirements is that an active directory group is created in the root-domain during the deployment. 

Is it possible that the client generates a customized status message during the deployment?

So I can use this unique status message in the “Status  Filter Rules” set. When the status message is uploaded to site server starts a powershell script.

I have already created the PowerShell script that created the Active Directory

Thank you


Correct Methods for International OSD?

$
0
0

Quick background rundown: I maintain the SCCM environment in our corporate office located in the US. The biggest pain in our environment is the differences in OS deployments to our 25-ish international locations. I now have distribution points at the main hubs with OSD capabilities.

I have 2 .wim images currently - standard image and engineering image with everything fully baked (~7GB and ~9GB respectively). This is to save on imaging time (and also due to software installs during the task sequence has never worked properly for me) so those are reasons for fully baked.

Our Germany location is now complaining that they have to spend a lot of time to "German-ize" my image after imaging, and will continue their old "OEM Out-of-Box" deployments because of this. Because of this, I've been instructed to re-evaulate my methods to accommodate our Italian, Brazilian, German, etc etc locations.

My question then is how do you folks with larger companies handle multi-language environments? Do you have separate .wim images for each location or do you load language packs and foreign installs of software as part of task sequences?

Examples of changes needed:
German Windows Language Pack and Keyboard

German Office Language Pack

Standard software (Reader for example) installed as German

Regional settings for Windows (time zone, etc)

sccm 2012 r2 mdt 2013 integration win 7 refresh

$
0
0

hi ,

I am trying to refresh win 7 and I tried all..  its always  apply to d: drive 

when I deploy win 7 ts to a new computer alone without refresh its worked ok and apply to c: drive

appreciate any help


Required Configuration for OSD

$
0
0

HI ,

I am getting Error-  PXE-E53: No boot filename received. while booting for PXE for the OSD from SCCM 2012 R2..

Even client machines are unable to take DHCP during PXE boot for the Boot..but same machines are able to take IP from DHCP server in windows os mode..

My sccm server 2012 R2 is on different subnet and DHCP + client machines are are different subnet ..

SCCM Server =192.169.0.0

DHCP Server + Client Machines for OSD= 192.168.0.

please suggest for the required configuration step by step from network/DHCP server level.



Shailendra Dev

OSD task sequence computer doesn't join domain - error NetJoinDomain failed error code is [1355]

$
0
0

I am using sccm 2012R2 and trying to deploy a task sequence to Ultrabook UEFI with usb Ethernet adaptor

I have inject network drivers in boot image and in sccm.

Task sequence runs fine till Setup Windows and Configuration. After this step computer reboots and boots in windows with local administrator account. Doesn't join to domain

I have tried ping domain and domain controller during Apply network Settings, I can ping fine and get an ip address as well.

setuperr.log file shows following error:

[Djoin.exe] Unattented Join: NetJoinDomain failed error code is [1355]

I can image other computer using x86 bootimage fine.

It is x64 boot image with UEFI Task sequence which is causing issues for me.

I have tested domain join AD account and able to do domain join same machine manually.

Need advise, not getting anywhere, already spend few days to figure out.

RJ


RJ09

Windows 8.1 OSD with MDT

$
0
0

Hi Guys,

I have a Test Environment (before deploying Live) were I am testing deployment of Windows 8.1 using MDT and SCCM 2012 R2.

We have created a User Driven MDT Task Sequence. We have our captured Image which has to images within the WIM File Image (1-1) and (2-2) OS Image.

We have setup the Task Sequence to apply image 2-2 to Disk 0, Partition 0. After the image has been applied the computer fails to boot. No error messages show before the computer re-boots and we get the message 'No Operating System was found'.

A few things that I have noticed when running the Task Sequence;

1) The install Image is always 'Windows 7 RMT' does this matter?

2) The Task Sequence doesn't show any errors before the it finishes, is there somewhere that might tell me more information about the Task Sequences Success?

Things I am going to look at tonight:

I am going to boot the computer using a WinPE Disk and see if the OS Image has applied to the Computer on Disk 0 Part 2 or if there is something else that is going on.

Any suggestion that might help with fixing this issue would be excellent.

Kind Regards,


TPark IT Technician

set registry tattoo

$
0
0

set registry tattoo i mean just i want to create a registry to know when OS is deployed, image version etc, it possible to set image version in my computer--properties like image version is 2

SCCM 2012 R2 extract failing

$
0
0

Greetings all.  We're trying to extract a reference machine for OS deployment in SCCM 2012 R2. System is a Dell 3010 with Windows 7 32 bit. We removed the CCM client just in case there was a conflict.

We modified the x86 boot image to enable command support. However, pressing F8 and launching the ISO and catching it at reboot does nothing. The menu comes up, but selecting "Safe Mode with Command Prompt" doesn't get me a command prompt?

Anyway, the snippet below is typical of what we see. The log indicates the machine successfully connected to the share and starts to capture an image and then very quickly bombs with the ...70002 error.

Is it trying to extract something from the Windows install and failing? Any insight would be appreciated. Thanks.

-------------------------------------------------------------------------------------------------------------------------------------------

[Successfully loaded the BCD boot system]LOG]!><time="12:17:41.231+480" date="02-19-2015" component="CaptureSystemImage" context="" type="1" thread="1892" file="bootsystem.cpp:1082">
<![LOG[Connection request for "\\cpn2.och.lan\d$\capture1"]LOG]!><time="12:17:41.388+480" date="02-19-2015" component="CaptureSystemImage" context="" type="1" thread="1892" file="tsconnection.cpp:208">
<![LOG[Connecting to "\\cpn2.och.lan\d$\capture1"]LOG]!><time="12:17:41.388+480" date="02-19-2015" component="CaptureSystemImage" context="" type="1" thread="1892" file="tsconnection.cpp:268">
<![LOG[Successfully connected to "\\cpn2.och.lan\d$\capture1"]LOG]!><time="12:17:43.739+480" date="02-19-2015" component="CaptureSystemImage" context="" type="1" thread="1892" file="tsconnection.cpp:287">
<![LOG[Creating image file \\cpn2.och.lan\d$\capture1\win7x86cap.wim]LOG]!><time="12:17:43.739+480" date="02-19-2015" component="CaptureSystemImage" context="" type="1" thread="1892" file="wimfile.cpp:377">
<![LOG[Starting system capture...]LOG]!><time="12:17:43.762+480" date="02-19-2015" component="CaptureSystemImage" context="" type="1" thread="1892" file="capturesystemimage.cpp:890">
<![LOG[Adding logical drive: C:]LOG]!><time="12:17:43.762+480" date="02-19-2015" component="CaptureSystemImage" context="" type="1" thread="1892" file="diskutils.cpp:1537">
<![LOG[Adding logical drive: D:]LOG]!><time="12:17:43.762+480" date="02-19-2015" component="CaptureSystemImage" context="" type="1" thread="1892" file="diskutils.cpp:1537">
<![LOG[Skipping non-local logical drive: E:]LOG]!><time="12:17:43.762+480" date="02-19-2015" component="CaptureSystemImage" context="" type="1" thread="1892" file="diskutils.cpp:1543">
<![LOG[Skipping non-local logical drive: X:]LOG]!><time="12:17:43.762+480" date="02-19-2015" component="CaptureSystemImage" context="" type="1" thread="1892" file="diskutils.cpp:1543">
<![LOG[Adding logical drive: C:]LOG]!><time="12:17:43.762+480" date="02-19-2015" component="CaptureSystemImage" context="" type="1" thread="1892" file="diskutils.cpp:1537">
<![LOG[Adding logical drive: D:]LOG]!><time="12:17:43.762+480" date="02-19-2015" component="CaptureSystemImage" context="" type="1" thread="1892" file="diskutils.cpp:1537">
<![LOG[Skipping non-local logical drive: E:]LOG]!><time="12:17:43.762+480" date="02-19-2015" component="CaptureSystemImage" context="" type="1" thread="1892" file="diskutils.cpp:1543">
<![LOG[Skipping non-local logical drive: X:]LOG]!><time="12:17:43.762+480" date="02-19-2015" component="CaptureSystemImage" context="" type="1" thread="1892" file="diskutils.cpp:1543">
<![LOG[regHalClass.Open( (HKEY)m_regControlSetKey, L"Control\\Class\\{4D36E966-E325-11CE-BFC1-08002BE10318}\\0000", ((((0x00020000L)) | (0x0001) | (0x0008) | (0x0010)) & (~(0x00100000L))) ), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\osdcore\offlineos.cpp,315)]LOG]!><time="12:17:43.827+480" date="02-19-2015" component="CaptureSystemImage" context="" type="0" thread="1892" file="offlineos.cpp:315">
<![LOG[ReferenceOs.getHalType(sHalType), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\capturesystemimage\capturesystemimage.cpp,312)]LOG]!><time="12:17:43.827+480" date="02-19-2015" component="CaptureSystemImage" context="" type="0" thread="1892" file="capturesystemimage.cpp:312">
<![LOG[CaptureHeaderImageOsInfo( iCurImage, DefaultOs, rInfo ), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\capturesystemimage\capturesystemimage.cpp,447)]LOG]!><time="12:17:43.827+480" date="02-19-2015" component="CaptureSystemImage" context="" type="0" thread="1892" file="capturesystemimage.cpp:447">
<![LOG[CaptureHeaderImageInfo(slVolumesToCapture, DefaultOs, Info), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\capturesystemimage\capturesystemimage.cpp,896)]LOG]!><time="12:17:43.827+480" date="02-19-2015" component="CaptureSystemImage" context="" type="0" thread="1892" file="capturesystemimage.cpp:896">
<![LOG[Failed to capture image metadata. 
The system cannot find the file specified. (Error: 80070002; Source: Windows)]LOG]!><time="12:17:43.827+480" date="02-19-2015" component="CaptureSystemImage" context="" type="3" thread="1892" file="capturesystemimage.cpp:896">


boot image X64

$
0
0
for boot image for e.g i am using windows7\8 x64 OS paltform so if i use boot image X64 (just for UEFI support) so i need to add all Network card drivers i am using DELL, HP, Lenovo, Panasonic models so i need to add all model Network cards drivers into boot image X64? again need to add hard disk drivers? hdc drivers?

OSD Task Sequence - Network boot capture of modified OS reference VM, but without MDT?

$
0
0

Hi All

Guess the Title of the question sums it up really.

Is it possible to do a network-boot (aka PXE) capture of an OS that has been modified, so that its WIM is created for use within other deployment Task Sequences?

I know that this is possible via MDT's "Sysprep and Capture" Task Sequence, but this integration has not been done yet, and from time-scales is not possible.  Just curious if others have found a work around via custom Task Sequence(s) of some kind?  If not will have to go with the SCCM's more manual 'Capture Media' option.

Any help much appreciated.

Kind Regards

Andrew

Boot loader resulting in 0xc0000017 error - no SCCM logs to refer to

$
0
0

I have had SCCM OSD working for over a year now.

Recently, we received some new models from Dell, so I added drivers into SCCM as I have done in the past.  With it, came new drivers for WinPE, which I also updated.

Since then, some sites (not all) have been seeing the following:
- boot to WinPE (initial):  No problem
- select task sequence:  No problem
- download initial WinPE wim:  No problem
- reboot to downloaded WinPE wim:  stops on boot machine with error 0xc000017 suggesting that hardware has changed and to reboot and try again.

This happens on any system in the affected offices.  As it happens outside of WinPE or Windows, there are no logs to refer to that I am aware of to help diagnose this.

The odd thing is that it does not happen in other locations... just 2 so far that I am aware of.

As it happened after a driver update to the boot image, I recreated the boot-image using previous driver set and assigned the newly created boot image to the task sequences.  No changes.

Has anyone ever encountered the 0xc0000017?

not sure what other info I could provide at this time.... any suggestions welcome.

Thanks!

Timed out waiting for ccmexec service to be fully operational

$
0
0

SCCM 2012 R2 CU4

About 30% of task sequences are 'getting stuck' with the above error, identical hardware, identical task sequence, but sometimes works but often does not. When I say getting stuck, i mean that the TS does not error out, it just appears to be stuck on a particular step (installing adobe reader for instance), which step varies, but in every case, when looking at the smsts.log you see that it has " Timed out waiting for ccmexec service to be fully operational"

Here is the error in the smsts.log

Policy verification done
Config policies compiled successfully
_SMSTSReturnToGINA variable set to true
Waiting for CcmExec service to be fully operational
Succeeded loading resource DLL 'C:\WINDOWS\CCM\1033\TSRES.DLL'
Timed out waiting for ccmexec service to be fully operational
0, HRESULT=80004005 (e:\qfe\nts\sms\framework\tscore\utils.cpp,4951)
Failed to wait for Ccmexec service to be fully operational (0x80004005)
hr = TS::Utility::WaitForCcmExec(g_hShutdownEvent), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanager.cpp,1524)


I am at a loss as to this cause of this one, the only change to the task sequence has been the inclusion of CU4, but i can clearly see that it is successfully installing on many machines, and the ccmsetup and client.msi logs show success.

Here is an example of a full log:  http://1drv.ms/1BXYu5J

Any help would be appreciated!!

Thanks.

RequestMPKeyInformation: Send() Failed

$
0
0

I have 12 DP's setup as PXE sites for image deployment. Everything is working great....except when I try to image off one of them it downloads the PE wim and starts up like its going to allow my to select my task seq....then fails and reboots. I can hit F8 and get into the SMSTS.log file and test network setting. I am able to ping my MP and DP no problem. What I am seeing in my log is it looks like the client isn't able to authenticate with the MP to get the key information. I am seeing:

401 - Unsuccessful with anonymous access retrying with context credentials

Using thread token for request

401 - Unsuccessful with context credentials. Retrying with supplied credentials.

Network access account credentials not supplied.

Now I know I have the network access account entered under software deployment, not 100% sure what context credentials are, and I verified in IIS anonymous access is enabled. And as I said things seem to be working fine at other locations. 

I was able to do images here not that long ago. To my knowledge there have been no changes made to the network.

I did try to remove PXE and WDS and reinstall but I didn't remove the whole DP role. Its on a slower connection so I didn't want to replicate everything again if I didn't have to. 

Viewing all 9126 articles
Browse latest View live