Jump to content


Aurock

Established Members
  • Content Count

    30
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Aurock

  • Rank
    Advanced Member
  1. Will this work in later parts of the task sequence, such as during the State Restore phase? Or does the F8 for cmd prompt only work during the WinPE phases?
  2. I'm trying to deploy Java 8 to our workstations for the first time, using v8u31. We currently have v7u71 installed. I ran the EXE and grabbed the msi from it's location in appdata like I normally do. I understand that there's no longer a cab file to go with the msi, it's all included in the msi file itself. I created an application and deployment type in SCCM from the msi file as normal, but it's failing to install. I've searched online a bit and found several posts with varying syntax to use for the command line, but after trying each one I'm still getting the same failure with return code 1603. I tried installing manually from a command prompt using one of the same command lines that was failing, and was able to install it successfully. Has anyone here been able to successfully deploy a recent version of Java as an application through SCCM? How did you do it? Here's the section of AppEnforce.log showing the install attempt: <![LOG[+++ Starting Install enforcement for App DT "Java 8 Update 31 - Windows Installer (*.msi file)" ApplicationDeliveryType - ScopeId_CADCA650-1EC0-4F91-96E4-EB2F3A11F57F/DeploymentType_7f67f2fc-8f14-4ccd-9c4f-759a278963a0, Revision - 12, ContentPath - C:\WINDOWS\ccmcache\7q, Execution Context - System]LOG]!><time="12:01:27.777+360" date="02-05-2015" component="AppEnforce" context="" type="1" thread="6996" file="appprovider.cpp:1702"> <![LOG[ A user is logged on to the system.]LOG]!><time="12:01:27.779+360" date="02-05-2015" component="AppEnforce" context="" type="1" thread="6996" file="appprovider.cpp:2083"> <![LOG[ Performing detection of app deployment type Java 8 Update 31 - Windows Installer (*.msi file)(ScopeId_CADCA650-1EC0-4F91-96E4-EB2F3A11F57F/DeploymentType_7f67f2fc-8f14-4ccd-9c4f-759a278963a0, revision 12) for system.]LOG]!><time="12:01:27.782+360" date="02-05-2015" component="AppEnforce" context="" type="1" thread="6996" file="appprovider.cpp:2148"> <![LOG[+++ Application not discovered. [AppDT Id: ScopeId_CADCA650-1EC0-4F91-96E4-EB2F3A11F57F/DeploymentType_7f67f2fc-8f14-4ccd-9c4f-759a278963a0, Revision: 12]]LOG]!><time="12:01:27.790+360" date="02-05-2015" component="AppEnforce" context="" type="1" thread="6996" file="localapphandler.cpp:291"> <![LOG[ App enforcement environment: Context: Machine Command line: msiexec /i jre1.8.0_31.msi WEB_JAVA=1 WEB_JAVA_SECURITY_LEVEL=H NOSTARTMENU=1 WEB_ANALYTICS=0 AUTO_UPDATE=0 EULA=0 SPONSORS=0 REBOOT=0 INSTALL_SILENT=1 Allow user interaction: No UI mode: 0 User token: null Session Id: 1 Content path: C:\WINDOWS\ccmcache\7q Working directory: ]LOG]!><time="12:01:27.790+360" date="02-05-2015" component="AppEnforce" context="" type="1" thread="6996" file="appcontext.cpp:85"> <![LOG[ Prepared working directory: C:\WINDOWS\ccmcache\7q]LOG]!><time="12:01:27.791+360" date="02-05-2015" component="AppEnforce" context="" type="1" thread="6996" file="appcontext.cpp:189"> <![LOG[Found executable file msiexec with complete path C:\WINDOWS\system32\msiexec.exe]LOG]!><time="12:01:27.794+360" date="02-05-2015" component="AppEnforce" context="" type="1" thread="6996" file="executility.cpp:188"> <![LOG[ Prepared command line: "C:\WINDOWS\system32\msiexec.exe" /i jre1.8.0_31.msi WEB_JAVA=1 WEB_JAVA_SECURITY_LEVEL=H NOSTARTMENU=1 WEB_ANALYTICS=0 AUTO_UPDATE=0 EULA=0 SPONSORS=0 REBOOT=0 INSTALL_SILENT=1 /qn]LOG]!><time="12:01:27.795+360" date="02-05-2015" component="AppEnforce" context="" type="1" thread="6996" file="appcontext.cpp:338"> <![LOG[Valid MSI Package path = C:\WINDOWS\ccmcache\7q\jre1.8.0_31.msi]LOG]!><time="12:01:27.797+360" date="02-05-2015" component="AppEnforce" context="" type="1" thread="6996" file="appcontext.cpp:765"> <![LOG[ Advertising MSI package [C:\WINDOWS\ccmcache\7q\jre1.8.0_31.msi] to the system.]LOG]!><time="12:01:27.798+360" date="02-05-2015" component="AppEnforce" context="" type="1" thread="6996" file="appcommon.cpp:125"> <![LOG[ Executing Command line: "C:\WINDOWS\system32\msiexec.exe" /i jre1.8.0_31.msi WEB_JAVA=1 WEB_JAVA_SECURITY_LEVEL=H NOSTARTMENU=1 WEB_ANALYTICS=0 AUTO_UPDATE=0 EULA=0 SPONSORS=0 REBOOT=0 INSTALL_SILENT=1 /qn with user context]LOG]!><time="12:01:29.123+360" date="02-05-2015" component="AppEnforce" context="" type="1" thread="6996" file="appexcnlib.cpp:205"> <![LOG[ Working directory C:\WINDOWS\ccmcache\7q]LOG]!><time="12:01:29.123+360" date="02-05-2015" component="AppEnforce" context="" type="1" thread="6996" file="appexcnlib.cpp:219"> <![LOG[ Post install behavior is BasedOnExitCode]LOG]!><time="12:01:29.129+360" date="02-05-2015" component="AppEnforce" context="" type="1" thread="6996" file="appcommon.cpp:1094"> <![LOG[ Waiting for process 3556 to finish. Timeout = 120 minutes.]LOG]!><time="12:01:29.132+360" date="02-05-2015" component="AppEnforce" context="" type="1" thread="6996" file="appexcnlib.cpp:2015"> <![LOG[ Process 3556 terminated with exitcode: 1603]LOG]!><time="12:01:34.744+360" date="02-05-2015" component="AppEnforce" context="" type="1" thread="6996" file="appexcnlib.cpp:2024"> <![LOG[ Looking for exit code 1603 in exit codes table...]LOG]!><time="12:01:34.745+360" date="02-05-2015" component="AppEnforce" context="" type="1" thread="6996" file="appexcnlib.cpp:508"> <![LOG[ Unmatched exit code (1603) is considered an execution failure.]LOG]!><time="12:01:34.745+360" date="02-05-2015" component="AppEnforce" context="" type="2" thread="6996" file="appexcnlib.cpp:594"> <![LOG[++++++ App enforcement completed (6 seconds) for App DT "Java 8 Update 31 - Windows Installer (*.msi file)" [ScopeId_CADCA650-1EC0-4F91-96E4-EB2F3A11F57F/DeploymentType_7f67f2fc-8f14-4ccd-9c4f-759a278963a0], Revision: 12, User SID: ] ++++++]LOG]!><time="12:01:34.747+360" date="02-05-2015" component="AppEnforce" context="" type="1" thread="6996" file="appprovider.cpp:2448"> The application log on the client shows this error: Log Name: Application Source: MsiInstaller Date: 2/5/2015 9:41:31 AM Event ID: 11722 Task Category: None Level: Error Keywords: Classic User: SYSTEM Computer: HP4429.davchc.com Description: Product: Java 8 Update 31 -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action installexe, location: C:\WINDOWS\Installer\MSIF890.tmp, command: /s INSTALLDIR="C:\Program Files (x86)\Java\jre1.8.0_31\\" EULA=0 AUTO_UPDATE=0 SPONSORS=0 REPAIRMODE=0 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="MsiInstaller" /> <EventID Qualifiers="0">11722</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2015-02-05T15:41:31.000000000Z" /> <EventRecordID>4510</EventRecordID> <Channel>Application</Channel> <Computer>HP4429.davchc.com</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data>Product: Java 8 Update 31 -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action installexe, location: C:\WINDOWS\Installer\MSIF890.tmp, command: /s INSTALLDIR="C:\Program Files (x86)\Java\jre1.8.0_31\\" EULA=0 AUTO_UPDATE=0 SPONSORS=0 REPAIRMODE=0 </Data> <Data>(NULL)</Data> <Data>(NULL)</Data> <Data>(NULL)</Data> <Data>(NULL)</Data> <Data>(NULL)</Data> <Data> </Data> <Binary>7B32364132344145342D303339442D344341342D383742342D3246383332313830333146307D</Binary> </EventData> </Event> Lastly, I'm attaching the jusched.log file from c:\windows\temp, which appears to be the java's own install log file. Unfortunately, I see in there that it failed, but don't see an indication of why. . . jusched.log
  3. For some reason my windows 7 deployment has suddenly stopped working properly. It gets to the installing updates phase, then gets almost all they way through downloading updates, then stalls. SMSTS.log has a bunch of “Waiting for job status notification” entries. I'll attach the entire log below. It looks like the same issue described in this blog post: http://configmgrblog.com/2012/05/30/osd-hanging-at-software-updates-installation-task-sequence-step/ Unfortunately, I applied updates to the reference image just a week or so ago. I believe the updates it's downloading to apply are probably for Office or other applications included in the reference image, and so they didn't get injected into the wim. I'm not sure if the issue is related to a single specific update, or if there's something else going on. What would cause this? smsts.log
  4. This question is prompted by, but not necessarily limited to, Java and it's frequent updates. What's the best way to configure an application in SCCM when new versions of the app are released and need to be deployed frequently? For Java, I've been creating a new Application in SCCM each time a new version comes out, naming it "Java 7 update 473" or whatever. I set it to supersede, and to uninstall the old version rather than upgrading. I deploy the new version, delete the deployment of the old version, and retire the application for the old version. Then, if I remember to, I go edit our OSD task sequence, removing the version of java from the Install Applications step and replacing it with the new version. If I forget, then the next time our desktop tech goes to re-image a machine it fails. That works, but it seems like there must be a better way. Preferably, an option that doesn't leave my Applications list with a dozen Retired application entries for versions of the same program. (I'm sure I can just delete the old ones at this point, but that's not really the point.) I considered just having one application for Java and creating a new Deployment type. Then I wouldn't have to update the OSD task sequence each time, or deploy new versions and retire old versions of the app each time. I'm not sure that would though, work since supersedence is configured at the application level. I need to be sure old versions get uninstalled when the new version goes in. How do others handle frequently updated applications such as this?
  5. I recently discovered that an outlook plugin I push out as an application through SCCM wasn't getting installed on some computers. Upon further investigation, I found that the deployment listed these computers as not meeting requirements. The requirement missing is listed as "Microsoft Office". That's the name of a dependency group I created, which contains Office 2010 and Office 2013. According to the text in the "Edit Dependency" window, this should mean that one or the other of those applications has to exist on the machine. Office 2010 is part of our standard image, and is on every workstation we put out. I confirmed that it is still installed on the workstation I'm using to troubleshoot this issue. Checking the properties of the deployment type used by the Office 2010 application, the detection method is set to check for the existence of MSI Product code {90140000-0011-0000-0000-0000000FF1CE}. On the affected computer, I searched the registry for that product code, and found it contained in the multi string value "ProductCodes" under key: HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Office14.PROPLUS The ProductCodes value contained multiple entries, as listed below: {90140000-0011-0000-0000-0000000FF1CE} {90140000-002C-0409-0000-0000000FF1CE} {90140000-00BA-0409-0000-0000000FF1CE} {90140000-002A-0000-1000-0000000FF1CE} {90140000-0044-0409-0000-0000000FF1CE} {90140000-001F-0C0A-0000-0000000FF1CE} {90140000-001B-0409-0000-0000000FF1CE} {90140000-0019-0409-0000-0000000FF1CE} {90140000-0117-0409-0000-0000000FF1CE} {90140000-0015-0409-0000-0000000FF1CE} {90140000-00A1-0409-0000-0000000FF1CE} {90140000-001F-0409-0000-0000000FF1CE} {90140000-001F-040C-0000-0000000FF1CE} {90140000-001A-0409-0000-0000000FF1CE} {90140000-0016-0409-0000-0000000FF1CE} {90140000-0018-0409-0000-0000000FF1CE} {90140000-0115-0409-0000-0000000FF1CE} {90140000-006E-0409-0000-0000000FF1CE} {90140000-002A-0409-1000-0000000FF1CE} {90140000-0116-0409-1000-0000000FF1CE} I also checked the appdiscover.log on the affected computer. There I find that it accurately detected Office 2010 as installed, and the plugin as not installed. What am I missing here? I've got about 60 workstations that don't have this plugin installed because SCCM thinks they don't meet requirements, but everything I can find says they do meet the requirements.
  6. I had issues with OSD after upgrading to SCCM 2012R2 as well. I ended up re-creating boot images, mdt packages, etc, and creating a new task sequence using those packages. Everything else in the task sequence was pretty much copied over from the previous one. Sorry I can't offer a better suggestion, but that did resolve the issues for me.
  7. I recently upgraded our SCCM server from 2012 SP1 to 2012R2. Since then, I've been struggling to get OSD working again. After creating a new task sequence, with new versions of the packages for USMT, settings, deployment tools, etc, I've got it mostly back up and going. The trouble now is that the task sequence seems to be downloading updates from windows update, not from the SCCM server. Looking in the SMSTS.log, I see a few errors, though I'm not sure they are related. Compiling AppManClientConfig policy... TSManager 6/10/2014 9:10:06 AM 1276 (0x04FC) Retrieving value from TSEnv for '_SMSTSAppManClientConfigPolicy' TSManager 6/10/2014 9:10:06 AM 1276 (0x04FC) ::DecompressBuffer(65536) TSManager 6/10/2014 9:10:06 AM 1276 (0x04FC) Decompression (zlib) succeeded: original size 982, uncompressed size 6358. TSManager 6/10/2014 9:10:06 AM 1276 (0x04FC) Instance path = 'CCM_ApplicationManagementClientConfig.SiteSettingsKey="1"' TSManager 6/10/2014 9:10:06 AM 1276 (0x04FC) Start to compile TS policy TSManager 6/10/2014 9:10:06 AM 1276 (0x04FC) Failed to find property 'AutoApplyDeployment' in 'CCM_ApplicationManagementClientConfig' class defintion. Error 0x80041002. Default value will be used for this property TSManager 6/10/2014 9:10:06 AM 1276 (0x04FC) Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace TSManager 6/10/2014 9:10:06 AM 1276 (0x04FC) End TS policy compilation TSManager 6/10/2014 9:10:06 AM 1276 (0x04FC) <...> pNAP->GetSystemIsolationInfo(&pNAPInfo, &bUnknownConnections), HRESULT=8027000c (e:\nts_sccm_release\sms\client\tasksequence\napcontrol\remediate.cpp,463) TSManager 6/10/2014 9:10:28 AM 1276 (0x04FC) GetSystemIsolationInfo(spNapClientInfo, &IsoStat), HRESULT=8027000c (e:\nts_sccm_release\sms\client\tasksequence\napcontrol\remediate.cpp,632) TSManager 6/10/2014 9:10:28 AM 1276 (0x04FC) Error getting system isolation info. Code 8027000C TSManager 6/10/2014 9:10:28 AM 1276 (0x04FC) ComputeComplianceAndRemediate(&QState), HRESULT=8027000c (e:\nts_sccm_release\sms\client\tasksequence\napcontrol\tsnapcontrol.cpp,48) TSManager 6/10/2014 9:10:28 AM 1276 (0x04FC) Remediation failed. Code 8027000C TSManager 6/10/2014 9:10:28 AM 1276 (0x04FC) hr = m_oNapCtrl.Remediate(QState), HRESULT=8027000c (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanager.cpp,1539) TSManager 6/10/2014 9:10:28 AM 1276 (0x04FC) Remediation failed with error code 8027000C TSManager 6/10/2014 9:10:28 AM 1276 (0x04FC) During the time that updates are being downloaded/installed, I don't see any errors. Here's the bit of the log file from that time. There are over 600 lines similar to the first few in this example: [613] Added/updated setting 'ccm_civersioninfo:modelname=site_cadca650-1ec0-4f91-96e4-eb2f3a11f57f/sum_fd7c7a92-93cb-47ba-a3a2-0ca6fcc345ba:version=203'. InstallSWUpdate 6/10/2014 9:14:49 AM 3028 (0x0BD4) [614] Added/updated setting 'ccm_civersioninfo:modelname=site_cadca650-1ec0-4f91-96e4-eb2f3a11f57f/sum_fdaa8e0b-63d2-4bbe-8209-a5526ce9bc86:version=203'. InstallSWUpdate 6/10/2014 9:14:49 AM 3028 (0x0BD4) [615] Added/updated setting 'ccm_civersioninfo:modelname=site_cadca650-1ec0-4f91-96e4-eb2f3a11f57f/sum_fe012160-7a31-44c8-a1ba-c6cdc184689a:version=202'. InstallSWUpdate 6/10/2014 9:14:49 AM 3028 (0x0BD4) [616] Added/updated setting 'ccm_civersioninfo:modelname=site_cadca650-1ec0-4f91-96e4-eb2f3a11f57f/sum_ff0d207d-29cd-44e8-88aa-3676f0c15bb9:version=202'. InstallSWUpdate 6/10/2014 9:14:49 AM 3028 (0x0BD4) [617] Added/updated setting 'ccm_civersioninfo:modelname=site_cadca650-1ec0-4f91-96e4-eb2f3a11f57f/sum_ff45265c-b98c-4104-8242-142580dd3fad:version=203'. InstallSWUpdate 6/10/2014 9:14:49 AM 3028 (0x0BD4) [618] Added/updated setting 'ccm_civersioninfo:modelname=site_cadca650-1ec0-4f91-96e4-eb2f3a11f57f/sum_ff845912-b926-463d-aa27-4a409412256b:version=203'. InstallSWUpdate 6/10/2014 9:14:49 AM 3028 (0x0BD4) Unlocked ActualConfig successfully InstallSWUpdate 6/10/2014 9:14:49 AM 3028 (0x0BD4) Unlocked policy transaction lock successfully InstallSWUpdate 6/10/2014 9:14:49 AM 3028 (0x0BD4) Raising event: instance of CCM_PolicyAgent_SettingsEvaluationComplete { ClientID = "GUID:D51C9558-680A-4FA7-82DB-681493D90486"; DateTime = "20140610141449.928000+000"; PolicyNamespace = "\\\\.\\root\\ccm\\policy\\machine\\actualconfig"; ProcessID = 3024; ThreadID = 3028; }; InstallSWUpdate 6/10/2014 9:14:49 AM 3028 (0x0BD4) Successfully submitted event to the Status Agent. InstallSWUpdate 6/10/2014 9:14:49 AM 3028 (0x0BD4) End TS policy evaluation InstallSWUpdate 6/10/2014 9:14:50 AM 3028 (0x0BD4) Policy evaluation initiated InstallSWUpdate 6/10/2014 9:14:50 AM 3028 (0x0BD4) GetIPriviledgedInstallInterface successful InstallSWUpdate 6/10/2014 9:14:50 AM 3028 (0x0BD4) Refreshing Updates InstallSWUpdate 6/10/2014 9:14:50 AM 3028 (0x0BD4) Successfully initiated RefreshUpdates operation InstallSWUpdate 6/10/2014 9:15:33 AM 3028 (0x0BD4) Waiting for RefreshUpdates complete notification from Updates Deployment Agent InstallSWUpdate 6/10/2014 9:15:33 AM 3028 (0x0BD4) Notification received, RefreshUpdates have been completed InstallSWUpdates 6/10/2014 9:25:46 AM 2424 (0x0978) Signaled RefreshComplete notification InstallSWUpdates 6/10/2014 9:25:46 AM 2424 (0x0978) Received RefreshUpdates complete notification from Updates Deployment Agent InstallSWUpdate 6/10/2014 9:25:46 AM 3028 (0x0BD4) RefreshUpdates operation has been completed, hr=0x00000000 InstallSWUpdate 6/10/2014 9:25:46 AM 3028 (0x0BD4) GetIPriviledgedInstallInterface successful InstallSWUpdate 6/10/2014 9:25:46 AM 3028 (0x0BD4) Installing all updates targetted for this computer InstallSWUpdate 6/10/2014 9:25:46 AM 3028 (0x0BD4) Checking if the active request handle: {DACCC970-DB1B-4113-8480-D959395BD826} is valid. InstallSWUpdate 6/10/2014 9:25:46 AM 3028 (0x0BD4) CoCreateInstance succeeded InstallSWUpdate 6/10/2014 9:25:46 AM 3028 (0x0BD4) Active request handle: {DACCC970-DB1B-4113-8480-D959395BD826} is valid. InstallSWUpdate 6/10/2014 9:25:46 AM 3028 (0x0BD4) Installation of updates started InstallSWUpdate 6/10/2014 9:25:51 AM 3028 (0x0BD4) Waiting for installation job to complete InstallSWUpdate 6/10/2014 9:25:51 AM 3028 (0x0BD4) Can anyone point me to where I might have gone wrong?
  8. I was checking up this morning on a deployment I had sent out to a test group last week, and found it showing 'error' state for 10 devices and unknown for the other 2. When I pull up the detailed deployment status, I see 4 computers listed on the 'error' tab, with 2 different errors, and 2 listed on the Unknown tab. The other tabs don't show any computers listed. I ran a report of computers in this test group that have this application installed, and the report shows 6 devices. Clearly it didn't hit an error everywhere, it's just the deployment status that's wrong. While looking into this, I noticed 2 other recent deployments also showing an error for all devices. For both of these other deployments, all tabs in the detailed 'deployment status' are empty, listing no computers. I happen to know that at least some of the target computers for these applications did install the deployed application successfully. I have run a summarization on all of these deployments, and refreshed to make sure I'm seeing current data, but still see the same status. I checked Site Status and Component Status in the sccm console, and everything is green for both. What would cause this incorrect data in deployment status?
  9. Found the solution. I had to add /b"c:\temp\appname" as an additional parameter. It seems that the installer wants to extract things into the user's local appdata directory, and when running from system center it can't do that - or can't get access to read back the files it extracted. By using the /b parameter to direct the extraction of files to a different location, the install now works successfully.
  10. Hmm... I created 'setup.cmd' and put the install command in the cmd file, using the variable as you suggested. I then changed the "Installation Program" to setup.cmd, updated conent for the application, and redistributed the application to the DP. Unfortunately, it's still failing to install, with a return code of -3. However, if I go to the ccmcache directory and manually run the 'setup.cmd' file as administrator, the program installs successfully with a return code of 0. What would cause the installer to return -3 (which appears to mean 'Required data not found in the Setup.iss file') when system center runs it, but not when I run it?
  11. I have some applications which have to be installed with a command line parameter that points to an answer file or config file. Typically, this parameter would include the full path to the required file. For example: setup.exe /s /path:"c:\temp\config.txt" To deploy it through config manager, I included the config.txt in the source directory alongside the setup.exe file. I have tried a couple of command line variations for the "Installation Program" in the deployment type for this, but I don't seem to have hit on the right one. What would be the proper syntax to use for installing such a program through configmgr, so that the program's setup routine can locate and access the required config file during installation? Thanks!
  12. Thanks for the reply. That doesn't seem to be the case in this instance. Checking the deployment type for this application, I'm showing Install Behavior is "Install for System", Logon Requirement is "Whether or not a user is logged on", and Installation program visibility is "Hidden". Ok, you rock. That was exactly the issue, except that there were 2 deployment types, and only one was set incorrectly. The x86 version, which is rarely used, was set to only install if the user is logged on. Changing the setting in that deployment type fixed the problem. Thanks!
  13. I'm trying to add an application to be installed during our OSD task sequence. The application is already set up in SCCM and deployed to all workstations. The box is also checked to allow the application to be installed from "install applications" step when not deployed. When I go to the "Install Applications" step in my task sequence and click the starburst button to add a new application to the list, I get a list of applications available in SCCM, but this one application is not in the list. Any idea why this might be? Thanks!
  14. I'm having trouble trying to refresh a computer from system center. I've been able to pxe boot and image this same laptop using the same task sequence. When I select the task sequence under "Installation Status" in Software Center and select reinstall, I get an error that the software could not be found on any servers at this time. Checking the cas log, I see "The number of discovered DPs(Including branch dp and multicast) is 0. Ok, so some content is not on the DP. But what? The lines directly above the error read: Requesting locations synchronously for content Content_b500a902-4f5b-463f-ab6d-27857ad49f20.1 with priority Medium ContentAccess 6/12/2013 11:37:03 AM 5552 (0x15B0) I was expecting a package ID number, but instead I got Content_b500a902-4f5b-463f-ab6d-27857ad49f20.1 How can I use that info to track down the content that it's looking for and can't find?
×
×
  • Create New...