Jump to content


Search the Community

Showing results for tags 'osd'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • Official Forum Supporters
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Windows Server 2008
    • Windows Server 2012
    • Windows Server 2016
    • Windows Server 2019
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

  1. We are working on deploying Server 2012 R2 via SCCM with Roles being installed based on the computer name. Our computer naming standards are "location-role-number" where the role is a 2 letter variable like WB for web server. In our task sequence we have added the following condition on the IIS role install... If ALL conditions are true: Task Sequence Variable OSDComputerName greater than or equals "%wb%. what we are seeing is that the IIS role will install on any server no matter what the name is. so clearly there's something wrong in the logic of the variable. Any help is greatly appreciated. Scott
  2. Hi , I am running into a issue when I try to deploy the task sequence to install operating system from secondary server. Here is my issue : In our environment we have 1 primary and 6 secondary site. Initially we built the primary site and tested the OS deployment . It went well without any issues . As the primary site is working fine we have configured other secondary sites . So I wanted to test the deployment s from Secondary server . For this I have changed the DHCP option 66 value to my secondary server IP. When I PXE boot the computer , I can see that the client is contacting the secondary server . This is the message I see on the client computer screen Contacting server : xx.xx.xx.xx TFTP download : smsboot\x64\abortpxe.com PXE boot aborted , booting to next device As the error is generic and was not much helpful , I checked SMSPXE.log in secondary server it says no advertisements found . I have attached SMSpxe.log . I have enabled PXE & Unknown computer support on secondary server . All the content is available on secondary site DP . I have restarted WDS service several times but it is of no use . I have tried this on 2-3 machines assuming the machine MAC id was stored in SCCM database . on every machine it is the same behavior . This is happening only with secondary server . If I change the option 66 value back to my primary server IP , the same deployment is working fine . I am struggling to find the cause for this behavior . Does any one has any idea on where should I look to resolve this problem or to dig deeper Thanks in Advance , Kishore SMSPXE.log
  3. We recently moved from 2007 to 2012 R2... as in 1 week after R2 release. Our consultant didn't know a ton about R2 so we had a few hiccups. I'm going to detail them here and see if any of you have any thoughts. SILVERLIGHT We have a sliverlight app that will not print on anything more advanced then silverlight 4. So we decided not to deploy silverlight with the client. Works fine... doesn't last a long time. Silverlight would upgrade or install (if not present) after a day or two. This is with us setting silverlight to NO update (app and registry and GPO) and not having it as part of the updates we download from WSUS. Not everyone uses the SL app but since we can't keep SL from upgrading if they do, we are stuck with two SCCM for the moment. This si problematical at best and using up resources we want to recover. OSD TS Deployment of Applications We have a number of task sequences that deploy a mixture of applications and packages. Even though the app will deploy afterwards we have occasional issues where a app will not install as part of the task sequence and there is no indication of anything wrong in the SMSTS.log file. Acts like the app was installed but its not. And if you check all the apps are on the local DP (and validated)... and as I said, I can deploy the app afterwards either separately or as part of another application TS. This tends to happen mostly to APPS, not packages. Office, Streets & Trips, Citrix reciever and a few others. And I'll have two identical machines, running on same port (different time) and one will get everything and one will miss half the apps. Also tried identical machines same time, different ports of same switch with same mixed results. These are all apps built form migrated packages; at most we went in and changed detection method after migration and conversion. Migrated apps and driver packages I am NOOB at SCCM, so forgives the NOOBNESS of this statement. I thought that if I took a TS and tried to Distribute Content to a DP or DP group and couldn't then all the apps and drivers were there and working. Same for driver and software packages; I thought if you distributed and didn't hear back, all was good. I found out I was wrong when we sent a DP to a remote site with limited bandwidth and realized the DP was falling back to boss SCCM box in our data center for a lot of (formerly migrated) software and driver packages. Upon diving in I found a good chunk of the migrated packages would not validate and ended up rebuilding the package (for software) and then redeploying (same source for software, same commands and settings just built into a package rather then migrated) and it worked. I am now looking at rebuilding most of our software and driver packages that were migrated. 0 Size Driver packages I have a number of newly created driver packages that have zero size. I have seen some posts on this but I have not seen a definitive answer. is this a error or is it indicative that the drivers are in other packages? 2007 Pushes We still have the bulk of the user base on 2007. However, most of the DPs (1 per AD site) have been moved to 2012 and do not work with 2007 anymore. I occasionally have clients in other AD sites fail to get software (will process when downloaded but never downloads). Should l recreate boundaries for each AD site and include the data center DP as a protected DP for each boundary? I have more issues that I am struggling with but this is enough for now. Any assistance, be they references to other posts or new wisdom, appreciated. Thanks!
  4. I seem to be getting a fairly common generic error but with possibly with a slight difference then some of the other problems/answers I have seen. Generally it looks like this is a DNS issue but I am not sure in my case. Let me 1st describe my infrastructure and what I am trying to accomplish. We use PKI on the main MPs/DPs. I have another DP that I will use for OSD content that won’t use PKI. I am 1st attempting to use boot media, vs PXE, to image a computer. I have distributed the content to the DP, created a boot media USB and everything looks good there as far as I can tell. My boot media selects the PKI MP and we have created the client cert and I direct it to the non-http DP. The process seems to accept the certificate and the boot media creation completes. Next boot off the media on the computer and drop into Windows PE where I can manually enter the IP information. When I click next the process fails. Error: Failed to Run Task Sequence An error occurred while retrieving policy for this computer (0x80004005). So starting some of the troubleshooting I F8. -Can I ping the SCCM site servers? Yes, I can ping, both short and FQDN, the primary, MP, DP. Looking at the SMSTSLog I see the following lines/errors. 1)Failed to open PXE registry key. Not a PXE boot. 2)Failed to find the source drive where WinPE was booted from But then the next line is: Executing from Media WinPE These 2 are at the top of the log and the process seems to continue on with the IP and variable information. These are the lines of information later in the log with the error(s): -CLibSMSMessageWinHTTPTransport::Send:URL: (my MP) -In SSL, but with no client cert -Error. Received 0x80072ee7 from WinHttpSendRequest. -Hr,HRESULT=80072ee7 -sending with winhttp failed, 80072ee7 -m_pHttp Transport -> (etc….) -MPKeyInformation.RequestMPKeyInformationForMedia -Failed to get information of MP: https//(my MP) So I am wondering where I start. I don’t see that unknown host line that seems to indicate that it is a DNS issue. I see some stuff about the in SSL but with no cert. Does this mean that the cert we had to create isn’t working correctly? We pretty much followed http://www.jamesbannanit.com/2012/05/how-to-build-and-capture-in-configuration-manager-2012-using-https/ I have also looked through this http://blogs.technet.com/b/configurationmgr/archive/2009/07/27/a-step-by-step-for-using-osd-through-system-center-configuration-manager-2007.aspx And I have pretty much everything done there except a network access account. Looking at my settings I am set to, “Use the computer account of the Configuration Manager client” However, my computer I am trying to image is a “WORKGROUP” and not joining the domain. But.. am I really getting that far in the process? Would I be failing to get policy because of this or does this just come into play when I try to get the OS from the DP?
  5. I have multiple DPs in my environment, but one in particular seems to be having issues with OSD. Right at the very start of the Task Sequence, it calls to download MDT Toolkit and immediately fails (log snippets below). I have uninstalled the DP and reinstalled it a couple of times, but this DP just can't seem to get past the MDT Toolkit. I have even redistributed the MDT Toolkit numerous times. On my other DPs, which followed the same procedures for setup, do not have this issue. Does anyone have any ideas? What worries me is these lines in the logs: socket 'connect' failed; 80072724d sending with winhttp failed; 80072efd Download() failed. 80072efd. Failed to resolve the source for SMS PKGID=LBT000D3, hr=0x80070002 Install Software failed to run command line, hr=0x80070002 Failed to run the action: Use Toolkit Package. The system cannot find the file specified. (Error: 80070002; Source: Windows) The system does have an active IP and can access the DP, so I am not sure why these are failing.
  6. We have been using OSD task sequences in SCCM 2012 for a few months without issue, recently however the task sequences will fail at the start. From logs, there is not enough free space to copy down the boot image as HD is full of partitions already evidently. I understand that if all packages in the task sequence have the checkbox enabled for "Copy the content in this package to a package share..." we would then get the option in the task sequence deployment to run content from DP rather than download locally, however this has never been set on our deployment(s) and we haven't had this issue before. I believe it should be able to PXE boot to the boot image (which clearly it is already doing prior to starting the task sequence), and for some reason something has changed which means it is trying to copy this locally and hence falling over. For the moment, we can run diskpart from f8 within the task sequence prior to commencing and remove existing partitions, at which point the OSD will complete successfully. Clearly, this would cause issues if we were doing user state migration, which we would like to deploy soon. Any ideas on where to start diagnosing this? I've had no luck tracking down what has changed to alter the behaviour.
  7. Hi guys I'm at the end of my wits here. For some reason I just cannot install any Software Packages, regardless of type (straight from exe, cmd file, etc), and regardless of program. I have tried recreating the packages from scratch, recreating my OSD task sequence from scratch, redistributing my Windows image, recreating it even, but nothing fixes my issue. In the packages themselves, I have ticked the "Allow this program to be installed from the Install Package task sequence without being deployed". I even tried deploying the package to the "All Systems" group in case the prior setting was being ignore, but it still doesn't work. I even deployed it at the container my test system is in, and it still doesn't work. All packages are set to run whether or not a user is logged on. The packages can deploy successfully when pushed out to running clients, it's only in an OSD task sequence that they fail. Here is a grab from the smsts.log file. ]LOG]!><time="07:20:32.668-660" date="11-03-2012" component="InstallSoftware" context="" type="1" thread="2088" file="event.cpp:729"> <![LOG[successfully submitted event to the Status Agent.]LOG]!><time="07:20:32.761-660" date="11-03-2012" component="InstallSoftware" context="" type="0" thread="2088" file="event.cpp:747"> <![LOG[End TS policy evaluation]LOG]!><time="07:20:32.777-660" date="11-03-2012" component="InstallSoftware" context="" type="1" thread="2088" file="policyutil.cpp:10580"> <![LOG[Policy evaluation initiated]LOG]!><time="07:20:32.777-660" date="11-03-2012" component="InstallSoftware" context="" type="1" thread="2088" file="utils.cpp:3387"> <![LOG[Waiting for policy to be compiled in 'root\ccm\policy\machine' namespace ]LOG]!><time="07:20:32.777-660" date="11-03-2012" component="InstallSoftware" context="" type="1" thread="2088" file="installsoftware.cpp:370"> <![LOG[Query path = 'CCM_SoftwareDistribution.ADV_AdvertisementID="BUN2007B",PRG_ProgramID="Add WSUS cert to root store",PKG_PackageID="BUN0003B"']LOG]!><time="07:20:32.777-660" date="11-03-2012" component="InstallSoftware" context="" type="1" thread="2088" file="installsoftware.cpp:401"> <![LOG[Verified policy is compiled in 'root\ccm\policy\machine' namespace]LOG]!><time="07:20:32.777-660" date="11-03-2012" component="InstallSoftware" context="" type="1" thread="2088" file="installsoftware.cpp:426"> <![LOG[content location count = 1]LOG]!><time="07:20:32.808-660" date="11-03-2012" component="InstallSoftware" context="" type="1" thread="2088" file="installsoftware.cpp:231"> <![LOG[invoking Execution Manager to install software ]LOG]!><time="07:20:32.808-660" date="11-03-2012" component="InstallSoftware" context="" type="0" thread="2088" file="installsoftware.cpp:233"> <![LOG[FALSE, HRESULT=87d02004 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\installsoftware.cpp,251)]LOG]!><time="07:20:32.855-660" date="11-03-2012" component="InstallSoftware" context="" type="0" thread="2088" file="installsoftware.cpp:251"> <![LOG[Failed to invoke Execution Manager to Install Software for PackageID='BUN0003B' ProgramID='Add WSUS cert to root store' AdvertID='BUN2007B' hr=0x87d02004]LOG]!><time="07:20:32.855-660" date="11-03-2012" component="InstallSoftware" context="" type="3" thread="2088" file="installsoftware.cpp:251"> <![LOG[installSoftware failed, hr=0x87d02004]LOG]!><time="07:20:32.855-660" date="11-03-2012" component="InstallSoftware" context="" type="3" thread="2088" file="installsoftware.cpp:262"> <![LOG[0, HRESULT=87d02004 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\installsoftware.cpp,764)]LOG]!><time="07:20:32.855-660" date="11-03-2012" component="InstallSoftware" context="" type="0" thread="2088" file="installsoftware.cpp:764"> <![LOG[Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\BUN0003B]LOG]!><time="07:20:32.855-660" date="11-03-2012" component="InstallSoftware" context="" type="1" thread="2088" file="resolvesource.cpp:3527"> <![LOG[reference count 1 for the source C:\_SMSTaskSequence\Packages\BUN0003B before releasing]LOG]!><time="07:20:32.855-660" date="11-03-2012" component="InstallSoftware" context="" type="1" thread="2088" file="resolvesource.cpp:3534"> <![LOG[Delete source directory C:\_SMSTaskSequence\Packages\BUN0003B]LOG]!><time="07:20:32.855-660" date="11-03-2012" component="InstallSoftware" context="" type="1" thread="2088" file="resolvesource.cpp:3557"> <![LOG[Released the resolved source C:\_SMSTaskSequence\Packages\BUN0003B]LOG]!><time="07:20:32.855-660" date="11-03-2012" component="InstallSoftware" context="" type="1" thread="2088" file="resolvesource.cpp:3567"> <![LOG[pInstall->Install(sPackageID, sProgramName), HRESULT=87d02004 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\main.cpp,361)]LOG]!><time="07:20:32.855-660" date="11-03-2012" component="InstallSoftware" context="" type="0" thread="2088" file="main.cpp:361"> <![LOG[install Software failed, hr=0x87d02004]LOG]!><time="07:20:32.855-660" date="11-03-2012" component="InstallSoftware" context="" type="3" thread="2088" file="main.cpp:361"> <![LOG[Process completed with exit code 2278563844]LOG]!><time="07:20:32.870-660" date="11-03-2012" component="TSManager" context="" type="1" thread="3904" file="commandline.cpp:1098"> <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="07:20:32.870-660" date="11-03-2012" component="TSManager" context="" type="1" thread="3904" file="instruction.cxx:3011"> <![LOG[Failed to run the action: Install WSUS cert to root store. The software distribution policy was not found. (Error: 87D02004; Source: CCM)]LOG]!><time="07:20:32.886-660" date="11-03-2012" component="TSManager" context="" type="3" thread="3904" file="instruction.cxx:3102"> <![LOG[MP server http://myserver.site.com.au. Ports 80,443. CRL=false.]LOG]!><time="07:20:32.886-660" date="11-03-2012" component="TSManager" context="" type="1" thread="3904" file="utils.cpp:4855"> <![LOG[setting authenticator]LOG]!><time="07:20:32.917-660" date="11-03-2012" component="TSManager" context="" type="1" thread="3904" file="utils.cpp:4877"> <![LOG[set authenticator in transport]LOG]!><time="07:20:32.917-660" date="11-03-2012" component="TSManager" context="" type="1" thread="3904" file="libsmsmessaging.cpp:7592"> <![LOG[sending StatusMessage]LOG]!><time="07:20:32.948-660" date="11-03-2012" component="TSManager" context="" type="1" thread="3904" file="libsmsmessaging.cpp:4020"> <![LOG[setting message signatures.]LOG]!><time="07:20:32.964-660" date="11-03-2012" component="TSManager" context="" type="0" thread="3904" file="libsmsmessaging.cpp:1292"> <![LOG[setting the authenticator.]LOG]!><time="07:20:32.964-660" date="11-03-2012" component="TSManager" context="" type="0" thread="3904" file="libsmsmessaging.cpp:1322"> <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: myserver.site.com.au:80 CCM_POST /ccm_system/request]LOG]!><time="07:20:32.980-660" date="11-03-2012" component="TSManager" context="" type="1" thread="3904" file="libsmsmessaging.cpp:8422"> <![LOG[Request was succesful.]LOG]!><time="07:20:33.011-660" date="11-03-2012" component="TSManager" context="" type="0" thread="3904" file="libsmsmessaging.cpp:8758"> <![LOG[set a global environment variable _SMSTSLastActionRetCode=-2016403452]LOG]!><time="07:20:33.011-660" date="11-03-2012" component="TSManager" context="" type="0" thread="3904" file="executionenv.cxx:668"> <![LOG[set a global environment variable _SMSTSLastActionSucceeded=false]LOG]!><time="07:20:33.011-660" date="11-03-2012" component="TSManager" context="" type="0" thread="3904" file="executionenv.cxx:668"> <![LOG[Clear local default environment]LOG]!><time="07:20:33.011-660" date="11-03-2012" component="TSManager" context="" type="0" thread="3904" file="executionenv.cxx:807"> <![LOG[Let the parent group (Setup Operating System) decides whether to continue execution]LOG]!><time="07:20:33.042-660" date="11-03-2012" component="TSManager" context="" type="0" thread="3904" file="instruction.cxx:3211"> <![LOG[The execution of the group (Setup Operating System) has failed and the execution has been aborted. An action failed. Operation aborted (Error: 80004004; Source: Windows)]LOG]!><time="07:20:33.058-660" date="11-03-2012" component="TSManager" context="" type="3" thread="3904" file="instruction.cxx:2425"> <![LOG[Failed to run the last action: Install WSUS cert to root store. Execution of task sequence failed. The software distribution policy was not found. (Error: 87D02004; Source: CCM)]LOG]!><time="07:20:33.058-660" date="11-03-2012" component="TSManager" context="" type="3" thread="3904" file="engine.cxx:214"> <![LOG[MP server http://myserver.site.com.au. Ports 80,443. CRL=false.]LOG]!><time="07:20:33.058-660" date="11-03-2012" component="TSManager" context="" type="1" thread="3904" file="utils.cpp:4855"> <![LOG[setting authenticator]LOG]!><time="07:20:33.089-660" date="11-03-2012" component="TSManager" context="" type="1" thread="3904" file="utils.cpp:4877"> <![LOG[set authenticator in transport]LOG]!><time="07:20:33.089-660" date="11-03-2012" component="TSManager" context="" type="1" thread="3904" file="libsmsmessaging.cpp:7592"> <![LOG[sending StatusMessage]LOG]!><time="07:20:33.104-660" date="11-03-2012" component="TSManager" context="" type="1" thread="3904" file="libsmsmessaging.cpp:4020"> <![LOG[setting message signatures.]LOG]!><time="07:20:33.120-660" date="11-03-2012" component="TSManager" context="" type="0" thread="3904" file="libsmsmessaging.cpp:1292"> <![LOG[setting the authenticator.]LOG]!><time="07:20:33.120-660" date="11-03-2012" component="TSManager" context="" type="0" thread="3904" file="libsmsmessaging.cpp:1322"> <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: myserver.site.com.au:80 CCM_POST /ccm_system/request]LOG]!><time="07:20:33.120-660" date="11-03-2012" component="TSManager" context="" type="1" thread="3904" file="libsmsmessaging.cpp:8422"> <![LOG[Request was succesful.]LOG]!><time="07:20:33.136-660" date="11-03-2012" component="TSManager" context="" type="0" thread="3904" file="libsmsmessaging.cpp:8758"> <![LOG[Launching command shell.]LOG]!><time="07:21:25.786-660" date="11-03-2012" component="OSDSetupHook" context="" type="1" thread="824" file="debugwindow.cpp:202"> <![LOG[executing command: C:\WINDOWS\system32\cmd.exe /k]LOG]!><time="07:21:25.786-660" date="11-03-2012" component="OSDSetupHook" context="" type="1" thread="824" file="debugwindow.cpp:63"> <![LOG[executed command: C:\WINDOWS\system32\cmd.exe /k]LOG]!><time="07:21:25.817-660" date="11-03-2012" component="OSDSetupHook" context="" type="1" thread="824" file="debugwindow.cpp:80"> <![LOG[Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanager.cpp,756)]LOG]!><time="07:35:45.768-660" date="11-03-2012" component="TSManager" context="" type="0" thread="3904" file="tsmanager.cpp:756"> <![LOG[Task Sequence Engine failed! Code: enExecutionFail]LOG]!><time="07:35:45.768-660" date="11-03-2012" component="TSManager" context="" type="3" thread="3904" file="tsmanager.cpp:756"> <![LOG[****************************************************************************]LOG]!><time="07:35:45.768-660" date="11-03-2012" component="TSManager" context="" type="1" thread="3904" file="tsmanager.cpp:779"> <![LOG[Task sequence execution failed with error code 80004005]LOG]!><time="07:35:45.768-660" date="11-03-2012" component="TSManager" context="" type="3" thread="3904" file="tsmanager.cpp:780"> I've tried searching for error 87d02004, but Google gives me nothing of use. Here is my execmgr log: <![LOG[software Distribution site settings (CCM_SoftwareDistributionClientConfig) policy does not yet exist on the client. If the client is not yet registered, this is expected behavior.]LOG]!><time="07:49:31.848-660" date="10-31-2012" component="execmgr" context="" type="2" thread="3904" file="softdistpolicy.cpp:1398"> <![LOG[software distribution agent was enabled]LOG]!><time="07:49:49.227-660" date="10-31-2012" component="execmgr" context="" type="1" thread="3556" file="execreqmgr.cpp:6665"> <![LOG[A user has logged on.]LOG]!><time="08:24:25.218-660" date="10-31-2012" component="execmgr" context="" type="1" thread="572" file="execreqmgr.cpp:4893"> <![LOG[The logged on user is MININT-MU0CRRN\Administrator]LOG]!><time="08:24:25.327-660" date="10-31-2012" component="execmgr" context="" type="1" thread="572" file="execreqmgr.cpp:4911"> <![LOG[Policy arrived for child program Add WSUS cert to root store]LOG]!><time="07:20:32.808-660" date="11-03-2012" component="execmgr" context="" type="1" thread="280" file="execreqmgr.cpp:6847"> <![LOG[Creating mandatory request for advert BUN2007B, program Add WSUS cert to root store, package BUN0003B]LOG]!><time="07:20:32.824-660" date="11-03-2012" component="execmgr" context="" type="1" thread="3936" file="execreqmgr.cpp:3658"> <![LOG[Could not find the policy in WMI for package BUN0003B program Add WSUS cert to root store]LOG]!><time="07:20:32.839-660" date="11-03-2012" component="execmgr" context="" type="2" thread="3936" file="softdistpolicy.cpp:2829"> <![LOG[CreateMandatoryRequestRecursively failed at FindUserOrSystemPolicy Add WSUS cert to root store]LOG]!><time="07:20:32.839-660" date="11-03-2012" component="execmgr" context="" type="2" thread="3936" file="execreqmgr.cpp:3675"> <![LOG[Policy deleted for advertisement BUN2007B package BUN0003B program Add WSUS cert to root store]LOG]!><time="07:35:47.266-660" date="11-03-2012" component="execmgr" context="" type="1" thread="868" file="execreqmgr.cpp:6941"> <![LOG[Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="BUN0003B",ProgramID="Add WSUS cert to root store", actionType 45l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="07:35:47.266-660" date="11-03-2012" component="execmgr" context="" type="1" thread="868" file="event.cpp:410"> <![LOG[software Distribution site settings (CCM_SoftwareDistributionClientConfig) policy does not yet exist on the client. If the client is not yet registered, this is expected behavior.]LOG]!><time="07:35:48.904-660" date="11-03-2012" component="execmgr" context="" type="2" thread="3344" file="softdistpolicy.cpp:1398"> <![LOG[software distribution agent was disabled]LOG]!><time="07:35:48.904-660" date="11-03-2012" component="execmgr" context="" type="1" thread="3344" file="execreqmgr.cpp:6576"> <![LOG[ReleaseRequest - no request found in either the pending or the completed queue]LOG]!><time="07:35:48.904-660" date="11-03-2012" component="execmgr" context="" type="3" thread="3432" file="execreqmgr.cpp:8613"> <![LOG[softdist is still trying to delete the corresponding task from MTC]LOG]!><time="07:35:48.904-660" date="11-03-2012" component="execmgr" context="" type="1" thread="3432" file="execreqmgr.cpp:8615"> <![LOG[MTC task with id: {960C9B0D-2D8D-4526-990B-1F8A44F3ACF0} deleted successfully.]LOG]!><time="07:35:48.904-660" date="11-03-2012" component="execmgr" context="" type="1" thread="3432" file="execreqmgr.cpp:8625"> I notice there is this line "<![LOG[Could not find the policy in WMI for package BUN0003B program Add WSUS cert to root store]LOG]!><time="07:20:32.839-660" date="11-03-2012" component="execmgr" context="" type="2" thread="3936" file="softdistpolicy.cpp:2829">" could this be it? What does it mean? Please help!
  8. Hello, I'm fairly new to SCCM 2012, and have just followed AnyWeb's excellent guide to OSD. However on my test Thinkpad X1, once WinPE finishes and reboots, it installs devices, then during the screen "Setting up System Settings" an error comes up stating that an error has occurred, reboot and restart the install. I tried looking in the smsts.log, but that seems to stop with the WinPE portion of the install. Can anyone guide me in the right direction to continue troubleshooting? I have tried disabling the driver install and os updates steps in the task, but the issue remains. Thanks!
  9. Greetings All, I started a dialog with anyweb in PM about an issue I'm facing in my environment and the notion that this could be helpful to someone else escaped me. As per his recommendation, I'm opening the question to the forum. I am currently managing two SCCM environments: SCCM 2007 R3 and SCCM 2012 R2. As it stands, the 2012 environment is doing all the relatively straightforward things that one would expect (Application/Package deployment, Baseline Configuration, OSD, Windows Update management, and so forth). The functionality I'm having problems with now is the Build & Capture. The B&C process inexplicably drops out at random during the "Install Package" steps I've added for getting our standard software into the image. I initially thought this was related to one piece of software and disabled the package for further evaluation. As I tested more and more, I found that the same error would pop up at random places during the "Install Package" area. Windows loads in an incomplete configuration state and the task sequence never continues. Miscellaneous details: The same behavior can be observed across Windows 7/Windows 8/Windows 8.1 Build & Capture attempts. I'm initiating the task sequence via boot media as the 2007 environment as the network helpers are still pointing to the 2007 PXE server. The software packages that I'm attempting to utilize are configured to allow for installations during the task sequence without being deployed. The first recommendation to me was as follows: The setup string I was using was as follows: CCMSetup.exe /noservice /mp:SERVER90.ad.organization SMSSITECODE=GS2 FSP=SERVER91.ad.organization It was changed to: CCMSetup.exe /mp:SERVER90.ad.organization SMSSITECODE=GS2 FSP=SERVER91.ad.organization SMSMP=SERVER90.ad.organization The task sequence properties are as follows: SMSCACHESIZE=30000 PATCH="%_SMSTSMDataPath%\OSD\GS20003D\Hotfix\KB2905002\Client\x64\configmgr2012ac-r2-kb2905002-x64.msp" I double-checked the boundaries and the subnet range that the virtual machine falls under is within one of the boundaries of my site's boundary group. The SMSTS.log looks relatively benign with the exception of the following error, which presents itself numerous times: Failed to query CCM_SoftwareDistribution I've attached the SMSTS.log to this post. I changed the suffixes to something a bit more generic so as to maintain anonymity. Any help would be appreciated and a preemptive, public thanks to anyweb for already offering some ideas. smsts-20140226-093900 - Copy.log
  10. Hi All, I was wondering if you could help me in renaming PC's during deployment. I am just getting started with SCCM and OSD deployments. I have a basic working deployment that deploys drivers per model using a wmi query to find the model number. My (dell) desktops / laptops will install and join the domain to a specified OU. My problem is when i add the OSDcomputername task sequence variable %serialnumber% i get the following error just before it finishes the task sequence. "Windows could not parse or process the unattend answer file for pass [specialize]. The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows-Shell-Setup]." My task sequence settings have been attached if that helps. Enabled it and it breaks things, disabled it and it goes back to working again. 1) Firstly is this the correct way for automating PC renaming during deployment? 2) What are others doing to rename PC's during deployment? I have read a lot of posts on forums regarding this process including scripts etc but i cannot make any of them work via OSD. I have a working powershell script that i can run from the desktop that checks if the serial number (TAG) matches the computer name, if it does not it renames the computer to the Serial number (TAG). Then i join the domain but i would like this to be part of the task sequence so we dont have to revisit workstations. If anyone has a working solution for renaming PC's during deployment please let me know. Thanks for reading Regards Dave
  11. Hi All I am pleeding for a little guidance. I am in the process of putting together a new image for the educational establishment that I work for. Our setup is a single site server running Win 20012 R2 with SQL 2012 and SCCM 2012 R2. The server is running on V-Sphere 5.1 Everything has been working fine until I hit the deployment of windows 7 > joining domain > installing apps/packages I have had this working on an older version of Windows/SCCM 2012 however, that server was setup incorrectly and was causing more harm than good. Thus leading me to create a new server with the above config. The OS seems to be installing perfectly as well as the joining of the domain. I have deleted all apps and OS images/installers and recreated them many times. I have also distributed and re-distributed everything. The Network Access account verifies perfectly Please see the attached smsts.log from a machine and the basic task sequence. I am aware there are errors, I am looking for a solution to these errors. Should I look at using a MDT TS instead of the standard SCCM TS? 90% of the time I get the error Code 0x80004005 (It usually errors on the install of Office 2013) Any advice would be highly appreciated. PLEASE Many Thanks Edd smsts.log smsts-20140219-162335.log
  12. I just added a HTA to the beginning of the TS. I had this working for about a week and then when I got back in after the weekend I keep getting both these errors. I made sure the DPs were updates with the most current source path. I've done tons of research (obviously not enough) and can't figure out why I keep getting this error. It is really inconsistent. I've attached the SMSTS logs. Hope someone out there can help. smsts.log smsts-20140219-191607.log
  13. Previously we had a 32-bit Windows 7 image that was deployed through a TS. The domain join was accomplished through the Apply Network Settings task and has worked fine, and still does. I recently captured a 64-bit Windows 7 image and used the same task sequence, just changed the image package but the domain join does not happen. When I try to log in after the TS finishes, I get the error "The security database on the server does not have a computer account for the workstation trust relationship". What am I missing?
  14. Hello, everybody! We had a task sequence for x86 systems, I've dupliceted it and changed it to Winx64 by changing all that I need, except a part "Install or Upgrade ConfigManager Client 4.0". That package was made in 2009 and worked fine so I've decided to use it in my OSD too.(Anyway it should contain both x86 and x64 versions, right?) Everything was great till I've realised that SCCM Client wont work properly after computer added to domain. OSD installation succeeded, sccm client installation succeeded everything is succeeded but the ConfigManager Client wont work properly. Where should I search the problem? I don't understand why do I need to install SCCM ConfigManager Client during OSD if after adding a machine to domain it will be automatically installed. Thanks!
  15. I am trying to create a Japanese Windows 7 Professional SP1 x64 reference image with SCCM 2012 R2 OSD but it is failing. This support doc outlines the exact problem I'm having... http://support.microsoft.com/kb/2691543 . I can create English and French reference images using this task sequence I created with no problems. It is creating a reference image starting with the source code and installing updates and then capturing the image. The support doc says I should download the Japanese version of the Windows ADK 8.1 (it references Windows AIK but I figure the concept is the same) and then import the Japanese boot image into SCCM and use it with the task sequence that installs Japanese Windows 7 Pro. The only problem is that I can't figure out how to get the Japanese boot image. I go to the download page for the Windows ADK 8.1 and I choose Japanese as the download language. But the boot image included with the ADK after I've downloaded it is still English. I thought maybe adksetup was detecting the language of my local OS and installing the same version of the ADK so I installed Japanese Windows 7 and tried again. Everything in the Windows ADK setup is in Japanese but it still installs only the English version of the boot files. Does anyone know how I can get the Japanese boot files? Thanks,
  16. Hello There, I have been trawling the interweb for simple script to insert into our OSD, where or deployment techs can enter details for creating the computer association of Old/Source PC and the New/Destination PC. The script would then query SCCM for resouceID's and create the associations, as well as making the 2 inputs available as TS variables. I have been trying this, by merging various scripts I found (My scripting is hit and miss at best): http://verbalprocessor.com/2011/03/06/computer-association-script/ - does what I want, but using a file to import the data, and only runs from the SCCM server. http://myitforum.com/myitforumwp/2011/12/06/vbscript-for-computer-association-with-logging/ - also does what i want, but uses script arguments, and no computer to resourseID resolving. http://www.windows-noob.com/forums/index.php?/topic/5227-vbscript-and-hta-to-associate-computer-and-add-to-specific-collections/ - again, part of this seems, but I don't seem to be able to get it too work. High level I want to achive an offline capture of XP data, and save this directly to the new Win7 PC (Which would already be built) and then run the restore from the new PC. I realise SMP is the preferred method, however alot of our child sites have very little storage available, effectively using SMP - and I assume transfering the data directly to the new PC is faster. This is the inspiration: https://blogs.technet.com/b/deploymentguys/archive/2011/09/01/replace-scenario-alternative-for-usmt-migration.aspx If anyone knows of any resources that they have used sucessfully (or examples of this being achieved) it would be great to hear about them.
  17. We are currently running SCCM 2012 R2 on a Windows Server 2012 environment. We deploy Windows 8.1 - 64 bits through a task sequence. Our question is, is it possible to deploy a Wireless profile through a script/package during the OSD task sequence? I've fiddled around with a script using NETSH, and manually i'm able to import / export a profile. However, this only works in the current user context. Unfortunately you cannot use 'user context' driven packages in a task sequence. Is there another method? Thanks in advance.
  18. Hi, i need to migrate a number of cm07 osd task sequences to cm12 and they fail everytime on incompatible steps as i have mdt2010 installed on the cm07 primary. I wondered if anyone can advise on the easiest way to migrate these please? i've read that the easiest way is to: 1. upgrade cm07 to mdt 2012u1, 2. upgrade all the cm07 TS, 3. install and integrate mdt2012u1 to the cm12r2 primary, 4. and then migrate TS from cm07 to cm12r2, is this right or is there a better way? and can anyone point me to some instructions on the upgrade of mdt2010 to mdt2012u1 as well as how to upgrade the TS on cm07? i ask because i've read that it can be tricky to do! thanks.
  19. Hello, I'm having an issue in my System Center 2012 R2 OS deployment where it fails when it gets to the point of installing the client. In the CCMLOG, I get this error: "HTTPS Communication protocol must be enabled when client is internet enabled". I don't have internet client nor https enabled in my environment (MP nor DP) and not planning to enable it. I'm curious why the client is trying to use https? Help! Thanks!
  20. Hi all, A while ago we had to shut down WDS on all of our DP's due to a task being sent out to the wrong machines. When we started WDS up again, one of our DP's would not start the WDS service. I ended up removing the role and content from the DP and the DP's site server from SCCM and starting from scratch. Now when I try to OSD a machine in that building it fails with the following error: Windows Boot Manager Windows failed to start. <bla bla bla> File: \Boot\BCD Status 0xc000000f Info: An error occurred while attemptint to read the boot configuration data. If I take the machine to another building, it images fine. Imaging also worked fine before restarting WDS. When I look at the SMSPXE.log of the DP during a netboot, I see the following (I have attached the full log as well): [010.013.010.001:4011] Recv From:[010.013.130.191:68] Len:283 1635e70 MAC=08:2E:5F:22:7D:F1 SMBIOS GUID=97035800-4440-11E1-0000-082E5F227DF1 > Received DHCP Request Set media certificate in transport Set authenticator in transport Set authenticator in transport failed to receive response with winhttp; 80072ee2 Failed to get information for MP: http://CM.mydomain.com. 80072ee2. PXE::DB_InitializeTransport failed; 0x80004005 PXE::DB_LookupDevice failed; 0x80004005 Set media certificate in transport Set authenticator in transport Set authenticator in transport failed to receive response with winhttp; 80072ee2 Will retry in 5 second(s) Retrying... failed to receive response with winhttp; 80072ee2 <snip> End of retries failed to send the request Failed to send status message (80072ee2) Failed to send the status message PXE::DB_ReportStatus failed; 0x80072ee2 PXE Provider failed to process message. Unspecified error (Error: 80004005; Source: Windows) failed to receive response with winhttp; 80072efe End of retries failed to send the request PXE::DB_LookupDevice failed; 0x80072efe Also possibly related but when I check the content library with ContentLibraryExplorer.exe all of the regular content checks out except for MSC00001 and MSC00002 (The configuration manager client package) which show as "(PENDING)" Thanks in advance for any help you can give! Edit: This is SCCM2012, no SP1, no R2. SMSPXE-error.log
  21. I've run into a strange problem and I'm not sure if it's a bug or something isn't functioning properly or if it's just the way Config Mgr Clients work. If I boot WinPE from PXE or USB media and run an OSD task sequence multicast works perfect. If I run the same OSD task sequence from the ConfigMgr Client on a machine (which just downloads WinPE and then boots into it) when it reboots into WinPE it starts downloading the OS image via unicast instead of multicast. I'm using the exact same task sequence and WinPE boot image. The OS image is even set to "Transfer this package only via multicast". The SMSTS log does not indicate that it's attempting to start a multicast session, it just starts unicast. Any ideas?
  22. I work in an environment where there are different IT depts that handle different locations and what I would like to do is be able to limit the OSD task sequences that are visible at a location. Is that even possible?
  23. Hi, I have a really odd problem that I’ve never seen before when deploying an OSD TS to an HP ProBook 6560b. I’m deploying Windows 7 Enterprise 64bit using Confg Manager 2012 SP1. I have the latest driver pack for this model from HP (sp61783.exe), and the correct driver pack is selected in the TS using a WMI query. The driver package is installed OK, however the wrong NIC driver is installed. The NIC is an Intel 82579V (PCI\VEN_8086&DEV_1503), however the driver for the 82579LM (PCI\VEN_8086&DEV_1502) gets installed. Checking the setupapi.dev.log I can see that in the first boot session (i.e. after SCCM has copied the drivers to the driverstore and the laptop reboots to install the drivers) the hardware is detected as DEV_1502. The 82579LM driver is selected and installed, however the device fails to start. After the next reboot in the TS the setupapi.dev.log shows that it has detected DEV_1503 and the 82579V driver is installed and the device starts. Things I’ve tested so far: A driver package with only the NIC driver in case another driver was causing the issue. Installing no drivers at all – the device is still detected as the 82579LM. Creating a new driver package. Several different versions of the driver including the latest from Intel rather than HP. A different install.wim (the original just has IE9 slipstreamed, but I get the same result from the install.wim from the Win7 ISO). Running the TS using standalone media. A couple of interesting things: It’s not a hardware problem as it build correctly in our SCCM 2007 environment – using the same drivers. The same TS works correctly on a ProBook 6570b and this has the same 82579V NIC. If I install manually using the Windows 7 DVD the device is detected correctly as the 82579V. Any help VERY much appreciated! first_boot_dev_1502.txt second_boot_dev_1503.txt
  24. Hey guys, Just wanted to hear your thoughts on deploying applications during an OS deployment, how do you guys do it? Do you capture the referance image with applications in it, and then deploy it? Or do you deploy applications on top of a basic image like i do? Or do you do all applications as normal deployments after the OSD is done? Personally, I've always(sccm 2007 + 2012, win 7 and up) had my OS .wim file clean, so just windows in there, no applications in it at all, and use the add application step to add software, but I see alot of people add the applications to the images, is there any specific reason for that? From what I can see, it's easyer to maintain the system when having them separated, so when there is a new version of something, I just update the task sequence, instead of creating the referance image again or change the one you have. Do you save that much time deploying applications into the image first or is it just an old habbit? Would like to hear all your views on this one, might be more out there that wonder what is "best", what ways people do it, and why use different ways //Xandor
  25. Currently we have a task sequence working to install an image of Windows 7. We have created a new windows 7 image and would like to just use the same task sequence to do the deployment. I copied the existing task sequence, pasted it into sccm2012 and then just updated the image file with out new captured .wim. The task sequence works and installs the OS, but none of the software packages are being installed via the TS. Any ideas?
×
×
  • Create New...