tjwillians74

In SCCM 2012 R2 I have a Package Deployment (Could not get this particular deployment to work as an Application Deployment). Its an exe with switches to run quietly and no restart. I've noticed when I monitor this deployments node that the machines that already have the program installed end up with a 10006 message id and description of 60004 under the error tab. Can I do something to have them instead show up as success, compliant?

Anymore up to date packs we can import?

I thought the same thing, which line is considered the NOTE?

I've been trying to get an image of server 2008 R2 that I created a wim file for that is full patched to a new UEFI based server for a legacy application. I can manually install 2008 on this hardware if I do it via disc. I want to do it via SCCM 2012 deployment in the event I need to send an image down to it or its counterparts again. I've successfully deployed a 2012 R2 image to this server in the past as a test. I believe my challenge has something to do with my task sequence with a 2008 OS image going to a UEFI server. I have the settings in the server to do both UEFI and Legacy. Each time I try a new deployment I use diskpart to clean disk 0. I check to make sure the server name is not in the devices collection of SCCM as well. It usually never is. Looking for some suggestions to try next from those with more experience. I'm only a few months into SCCM so clearly I've missed something. I've enclosed 3 of the SMSTS.LOG files to this message in hopes someone can spot the error to better clarify what I am looking at. Here is what I see while it's working: UEFI Partition disk 0 Formatting C:\ Apply operating system Downloading wim Applying image 1 from wim to C:\ After the progress bar comes all the way to the right, it fails the task sequence 0x8004005 Greatly appreciative of this site and the members for the day 1 to where I am now in learning and using SCCM. lastrun__on_x_smsts.log lastrun__on_x2_smsts.log lastrun_smsts.log

In SCCM 2012 I select the Create Task Sequence Media Wizard, Create Task Sequence Media, Capture Media (Creates media used to capture an OS deployment image from a reference computer), CD/DVD set to create the ISO, select a boot image (anything to look out for here, other than 32 bit or 64 bit?), select an existing distribution point, click next, finish. Once ISO is created, I copy it to where the reference 2008 R2 VMM can attach to it on its virtual drive, and launch the TSMBautorun. Yes, I have gone through that article. :-)

I've been trying to capture a reference image from a hyper-v VM off a 2008 R2 server OS. It seems I'm able to capture the image, but the WIM file seems very small. Its only about 8MB and that's not right. In SCCM where I imported it under Operating Systems Images and then view properties I see it listed under Select Images You Want To View as 1 - None where as in the past I've seen that section in 2012 R2 list 1-1 and 2-2. Not sure what I am missing here. I'm running on a System Center 2012 R2 Configuration Manager SP1 with Windows ADK 8.1, and Microsoft Deployment Toolkit 2012 Update 1. I made the task sequence media ISO in SCCM and then went through the wizard in the 2008 R2 VM to create the WIM file. I'm trying to see what I may have overlooked or if maybe there is a better way to make this WIM file and get it into SCCM Operating Systems? Thanks for your suggestions.

Something interesting happened, I don't understand exactly why but it worked. Something I was doing that I changed was this. When at the add operating system image wizard, I had a path similar to this \\myserver\images\Server 2012 R2 Dell1\server2012r2dell1.wim and on the next screen under name I changed the default to "Server 2012 R2 Dell1" which was a direct copy and paste of the words in the path. When I did that it gave me an error, if I left it at the default name on the general screen of the add operating system image wizard, it let me add it. I could then go the properties of that OS image and change the name to something more descriptive. I've been able to add 3 more images since doing this.

I tried to bring a new image (wim file) into my configuration manager under operating system images folder. The wim file creation went fine using sccm task sequence media we created, but it errors on import. Looking for possible suggestions on whats causing this and how to act next. Error: Errors • The SMS Provider reported an error. • ConfigMgr Error Object: instance of SMS_ExtendedStatus { • CauseInfo = "3"; • Description = "CSspPkgProgram: DISTSRC_SQL_ERROR"; • ErrorCode = 3242722565; • File = "e:\\qfe\\nts\\sms\\siteserver\\sdk_provider\\smsprov\\ssppackage.cpp"; • Line = 1110; • Operation = "PutInstance"; • ParameterInfo = ""; • ProviderName = "ExtnProv"; • SQLMessage = "[23000][2627][Microsoft][SQL Server Native Client 11.0][SQL Server]Violation of PRIMARY KEY constraint 'SMSPackages_L_PK'. Cannot insert duplicate key in object 'dbo.SMSPackages_L'. The duplicate key value is (GC2000D3). : tr_SMSPackages_ins"; • SQLSeverity = 14; • SQLStatus = 2627; • StatusCode = 2147749889; };