Jump to content


Search the Community

Showing results for tags 'deployment'.



More search options

  • 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

Found 89 results

  1. Just tested this thing and I'm kind of thrilled.. so I wanted to deploy cmtrace as an CM12 application, I did it with the quick-and-dirty method. So, I created a new application, and for the deployment type I checked script and the actual install program was as follows xcopy.exe ".\*.*" "%windir%\system32" /D /E /C /I /Q /H /R /Y /S And the uninstall program was as follows del.exe %windir%\system32\cmtrace.exe Detection method was of course checking the presence of cmtrace in %windir%\system32. The niceness about this is, that now I can simply run cmtrace on any computer in the network and I was thinking that the new app-model is way better than the old package deployment, what do you guys think? Has anyone else thought about deploying software like this? I know it would be better to handle it by doing a script that installs the cmtrace to %programfiles% and so on...
  2. Hi all, I've tried and failed miserably! to work out how to do this using the Report Builder. Could anyone possibly help with creating an SQL query to create a deployment report which includes the Administrative Category? Example: Application Name, Application Administrative Category, Target Collection, Success, In Progress, Fail, Requirements not met, Unknown. Would really appreciate any assistance. Thanks
  3. Not sure if this is the standard behavior, but the current client version my systems are using is 5.00.8634.1814. However the version that is installing during imaging is not the latest version. Is there a way to resolve this during imaging, or do I just wait until the client upgrades itself? Thanks Jesse
  4. Scenario: Windows 10 ADK 1803, SCCM CBB 1802, build and capture TS, OS Deployment TS. I did a build and capture of Windows 10 1803 CBB (64 bit), I then added my newly captured image, and slipstreamed the updates into the image. Upon Deployment of said image, the image gets deployed but steps in my Task Sequence fail to run. There are these errors (I assume related to "Install Updates" TS step) Failed to find property 'WUfBEnabled' in 'CCM_SoftwareUpdatesClientConfig' class defintion. Error 0x80041002. Default value will be used for this property TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Failed to find property 'EnableThirdPartyUpdates' in 'CCM_SoftwareUpdatesClientConfig' class defintion. Error 0x80041002. Default value will be used for this property TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Failed to find property 'EnableExpressUpdates' in 'CCM_SoftwareUpdatesClientConfig' class defintion. Error 0x80041002. Default value will be used for this property TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Failed to find property 'ExpressUpdatesPort' in 'CCM_SoftwareUpdatesClientConfig' class defintion. Error 0x80041002. Default value will be used for this property TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Failed to find property 'ExpressVersion' in 'CCM_SoftwareUpdatesClientConfig' class defintion. Error 0x80041002. Default value will be used for this property TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Then these Failed to find property 'AutoApplyDeployment' in 'CCM_ApplicationManagementClientConfig' class defintion. Error 0x80041002. Default value will be used for this property TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Failed to find property 'EnableHealthAttestation' in 'CCM_ClientAgentConfig' class defintion. Error 0x80041002. Default value will be used for this property TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Failed to find property 'UseOnPremHAService' in 'CCM_ClientAgentConfig' class defintion. Error 0x80041002. Default value will be used for this property TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Failed to find property 'OnPremHAServiceUrl' in 'CCM_ClientAgentConfig' class defintion. Error 0x80041002. Default value will be used for this property TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Failed to find property 'GracePeriodHours' in 'CCM_ClientAgentConfig' class defintion. Error 0x80041002. Default value will be used for this property TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Then the next significant error Status Agent hasn't been initialized yet. Attempting to create pending event. TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Raising pending event: instance of CCM_PolicyAgent_SettingsEvaluationComplete { DateTime = "20180524231416.340000+000"; PolicyNamespace = "\\\\.\\root\\ccm\\policy\\machine\\actualconfig"; ProcessID = 4672; ThreadID = 4676; }; TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Successfully submitted pending event to WMI. TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) End TS policy evaluation TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Policy evaluation initiated TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Waiting for policy to be compiled in 'root\ccm\policy\machine' namespace TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Query = 'CCM_SoftwareUpdatesClientConfig.SiteSettingsKey="1"' TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Verified policy for instance path 'CCM_SoftwareUpdatesClientConfig.SiteSettingsKey="1"' compiled in 'root\ccm\policy\machine' namespace TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Query = 'CCM_SoftwareDistributionClientConfig.SiteSettingsKey="1"' TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Verified policy for instance path 'CCM_SoftwareDistributionClientConfig.SiteSettingsKey="1"' compiled in 'root\ccm\policy\machine' namespace TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Query = 'CCM_NetworkAccessAccount.SiteSettingsKey="1"' TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Verified policy for instance path 'CCM_NetworkAccessAccount.SiteSettingsKey="1"' compiled in 'root\ccm\policy\machine' namespace TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Query = 'CCM_NetworkAccessAccount.SiteSettingsKey="1"' TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Verified policy for instance path 'CCM_NetworkAccessAccount.SiteSettingsKey="1"' compiled in 'root\ccm\policy\machine' namespace TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Query = 'CCM_RebootSettings.SiteSettingsKey="1"' TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Verified policy for instance path 'CCM_RebootSettings.SiteSettingsKey="1"' compiled in 'root\ccm\policy\machine' namespace TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Query = 'CCM_ApplicationManagementClientConfig.SiteSettingsKey="1"' TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Verified policy for instance path 'CCM_ApplicationManagementClientConfig.SiteSettingsKey="1"' compiled in 'root\ccm\policy\machine' namespace TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Query = 'CCM_ClientAgentConfig.SiteSettingsKey="1"' TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Verified policy for instance path 'CCM_ClientAgentConfig.SiteSettingsKey="1"' compiled in 'root\ccm\policy\machine' namespace TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Policy verification done TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Config policies compiled successfully TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) _SMSTSReturnToGINA variable set to true TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Waiting for CcmExec service to be fully operational TSManager 5/24/2018 6:14:16 PM 4676 (0x1244) Succeeded loading resource DLL 'C:\WINDOWS\CCM\1033\TSRES.DLL' TSManager 5/24/2018 6:14:17 PM 4676 (0x1244) Timed out waiting for ccmexec service to be fully operational TSManager 5/24/2018 6:44:29 PM 4676 (0x1244) 0, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,5208) TSManager 5/24/2018 6:44:29 PM 4676 (0x1244) Failed to wait for Ccmexec service to be fully operational (0x80004005) TSManager 5/24/2018 6:44:29 PM 4676 (0x1244) Specifically the following lines, where I believe the remainder of my issues spawn from? Timed out waiting for ccmexec service to be fully operational TSManager 5/24/2018 6:44:29 PM 4676 (0x1244) 0, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,5208) TSManager 5/24/2018 6:44:29 PM 4676 (0x1244) Failed to wait for Ccmexec service to be fully operational (0x80004005) TSManager 5/24/2018 6:44:29 PM 4676 (0x1244) Then I get down to my next step in my TS, where again I see the "timed out waiting..." message !--------------------------------------------------------------------------------------------! TSManager 5/24/2018 6:44:34 PM 4676 (0x1244) Expand a string: FullOS TSManager 5/24/2018 6:44:34 PM 4676 (0x1244) Executing command line: smsappinstall.exe /app:ScopeId_6BC60758-14AB-484E-8AF3-71922ADE2F4A/Application_b0178a91-358a-48e2-9ca5-343894032d5b,ScopeId_6BC60758-14AB-484E-8AF3-71922ADE2F4A/Application_7d3731d2-bf9a-4c2c-9b1e-e0e8a014bc8c,ScopeId_6BC60758-14AB-484E-8AF3-71922ADE2F4A/Application_cd92f8fa-35b3-406f-9714-9923942705bc,ScopeId_6BC60758-14AB-484E-8AF3-71922ADE2F4A/Application_f45cbbaf-4bea-44ea-bcff-1442e606442d,ScopeId_6BC60758-14AB-484E-8AF3-71922ADE2F4A/Application_c8b54e20-cde4-4665-9033-6842ed0ab1eb,ScopeId_6BC60758-14AB-484E-8AF3-71922ADE2F4A/Application_be480c85-3c63-460c-95df-2f314c662a95,ScopeId_6BC60758-14AB-484E-8AF3-71922ADE2F4A/Application_4ec3cc05-3815-46f2-8ebd-3cf3d1d91276,ScopeId_6BC60758-14AB-484E-8AF3-71922ADE2F4A/Application_9f1c5056-8d95-4830-85ca-3fb42f21fdda,ScopeId_6BC60758-14AB-484E-8AF3-71922ADE2F4A/Application_64069075-99d6-47c2-8fbd-1864d0cfac12 /basevar: /continueOnError:True TSManager 5/24/2018 6:44:34 PM 4676 (0x1244) [ smsinstallapp.exe ] InstallApplication 5/24/2018 6:44:34 PM 972 (0x03CC) Application Names: InstallApplication 5/24/2018 6:44:34 PM 972 (0x03CC) 'ScopeId_6BC60758-14AB-484E-8AF3-71922ADE2F4A/Application_b0178a91-358a-48e2-9ca5-343894032d5b' InstallApplication 5/24/2018 6:44:34 PM 972 (0x03CC) 'ScopeId_6BC60758-14AB-484E-8AF3-71922ADE2F4A/Application_7d3731d2-bf9a-4c2c-9b1e-e0e8a014bc8c' InstallApplication 5/24/2018 6:44:34 PM 972 (0x03CC) 'ScopeId_6BC60758-14AB-484E-8AF3-71922ADE2F4A/Application_cd92f8fa-35b3-406f-9714-9923942705bc' InstallApplication 5/24/2018 6:44:34 PM 972 (0x03CC) 'ScopeId_6BC60758-14AB-484E-8AF3-71922ADE2F4A/Application_f45cbbaf-4bea-44ea-bcff-1442e606442d' InstallApplication 5/24/2018 6:44:34 PM 972 (0x03CC) 'ScopeId_6BC60758-14AB-484E-8AF3-71922ADE2F4A/Application_c8b54e20-cde4-4665-9033-6842ed0ab1eb' InstallApplication 5/24/2018 6:44:34 PM 972 (0x03CC) 'ScopeId_6BC60758-14AB-484E-8AF3-71922ADE2F4A/Application_be480c85-3c63-460c-95df-2f314c662a95' InstallApplication 5/24/2018 6:44:34 PM 972 (0x03CC) 'ScopeId_6BC60758-14AB-484E-8AF3-71922ADE2F4A/Application_4ec3cc05-3815-46f2-8ebd-3cf3d1d91276' InstallApplication 5/24/2018 6:44:34 PM 972 (0x03CC) 'ScopeId_6BC60758-14AB-484E-8AF3-71922ADE2F4A/Application_9f1c5056-8d95-4830-85ca-3fb42f21fdda' InstallApplication 5/24/2018 6:44:34 PM 972 (0x03CC) 'ScopeId_6BC60758-14AB-484E-8AF3-71922ADE2F4A/Application_64069075-99d6-47c2-8fbd-1864d0cfac12' InstallApplication 5/24/2018 6:44:34 PM 972 (0x03CC) BaseVar = '', ContinueOnError='True' InstallApplication 5/24/2018 6:44:34 PM 972 (0x03CC) SwdAction = '0001' InstallApplication 5/24/2018 6:44:34 PM 972 (0x03CC) Waiting for CcmExec service to be fully operational InstallApplication 5/24/2018 6:44:34 PM 972 (0x03CC) Succeeded loading resource DLL 'C:\WINDOWS\CCM\1033\TSRES.DLL' InstallApplication 5/24/2018 6:44:35 PM 972 (0x03CC) Timed out waiting for ccmexec service to be fully operational InstallApplication 5/24/2018 7:14:49 PM 972 (0x03CC) 0, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,5208) InstallApplication 5/24/2018 7:14:49 PM 972 (0x03CC) Failed to wait for Ccmexec service to be fully operational (0x80004005) InstallApplication 5/24/2018 7:14:49 PM 972 (0x03CC) TS::Utility::WaitForCcmExec(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\main.cpp,253) InstallApplication 5/24/2018 7:14:49 PM 972 (0x03CC) Process completed with exit code 2147500037 TSManager 5/24/2018 7:14:49 PM 4676 (0x1244) !--------------------------------------------------------------------------------------------! TSManager 5/24/2018 7:14:49 PM 4676 (0x1244) Failed to run the action: Install Applications. Unspecified error (Error: 80004005; Source: Windows) TSManager 5/24/2018 7:14:49 PM 4676 (0x1244) 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) TSManager 5/24/2018 7:14:49 PM 4676 (0x1244) Failed to run the last action: Install Applications. Execution of task sequence failed. Unspecified error (Error: 80004005; Source: Windows) TSManager 5/24/2018 7:14:49 PM 4676 (0x1244) And then my TS step fails to run the "Install Applications" step. I assume the issue is completely related to the client failing to install properly - My question is how can I fix this? What I have done so far is: Update the boot image to the latest version (10.0.17134.1) Used the default Config Manager package in my build and capture, and OS Deployment TS, specifying the SMSMP Tested deploying the image again - Each time the same issues occur, the client fails to install properly and looks like this when I get into Windows I have also attached a copy of SMSTS.log as well. Thanks for any assistance. smsts.log
  5. Hello everyone, I'm currently trying to learn about SCCM and deploying Windows 10 using PXE and MDT, however my clients never seem to get to the task sequence part, instead they just reboot when it says "Preparing network connections". I am able to stop the reboot by pressing F8 and it shows I have an ip, disk looks good using diskpart, can ping sccm fqdn and I'm able to use net use to map a share. I have crawled every possible forum and posts and nothing seems to help, and I really feel like everything is correct and should be working. I hope to get some help from you experts. The clients I have tried to deploy to are a Dell Optiplex 7040 client and Vmware VMs. I downloaded all the necessary drivers for the Optiplex 7040 and the vmxnet3 driver for the VM which I injected into the WinPE x64 boot image. I also tried to PXE boot without any driver in the boot image. I created a user in AD named SCCM_NAA which has been used as the network access account. The firewall has been completely turned off on the SCCM server. Deployed task sequence to All unknown computers and a collection called Windows 10 Deployment containing PC02. SMSTS.log (included in post) - All clients always show the same three possible errors PxeGetPxeData failed with 0x80070005 RegOpenKeyExW is unsuccessful for Software\Microsoft\SMS\Task Sequence GetTsRegValue() is unsuccessful. 0x80070002. The guide I've been using to set everything up this one: www.windows-noob.com/forums/topic/14057-how-can-i-deploy-windows-10-with-mdt-2013-update-2-integrated-with-system-center-configuration-manager-current-branch/ Lab setup is as follows, all MSDN media: SCCM01 - SCCM Server 1702 - Server 2016 SQL01 - SQL Server for SCCM - SQL Server 2016 DC01 & DC02 - AD, DNS and DHCP set up with option 066 and 067 configured pointing to the SCCM server and SMSboot\x64\wdsnbp.com Dell OptiPlex 7040 - Client PC02 (VM) - Member of SCCM server as a client PC03 (VM) - Newly created VM with no OS, but has a virtual HDD attached Boot image and operating system image Task sequence smsts_PC02.log
  6. May I ask for your help please? Capture image was successfully imaged using DISM (.wim file) and deployed it successfully however the restore partition is missing on the deployed PC. Can I ask for your recommendations please. For reference please see details: Windows server 2012 dell OS (captured image) Windows 10 x64 PC dell micro 7050
  7. Hi, I have a headache with an extrange issue. I have deployed a Task Sequence time ago, this week i delete it and deployed a new one as i have done previously.Now i still see available both. First i checked the TS status and i reviewed that is not deployed to any collection. I disabled it too but still visible for clients (PXE). I thinks that is cached on DP or in the Databaseany suggestions? I attach some screens thanks
  8. Hi, I have a headache with an extrange issue. I have deployed a Task Sequence time ago, this week i delete it and deployed a new one as i have done previously.Now i still see available both. First i checked the TS status and i reviewed that is not deployed to any collection. I disabled it too but still visible for clients (PXE). I thinks that is cached on DP or in the Databaseany suggestions? I attach some screens thanks
  9. Are you planning to deploy Microsoft Intune and looking for straightforward technical guidance to help you accelerate this effort? Please join us as we share our deployment experience working with customers from all over the world, covering Intune pilot planning, deployment and management. At the end of this session, you will have a solid foundation to deliver a successful Intune pilot deployment in your organization. The above is a session I did with Peter Daalmans @ Microsoft Ignite on Friday 29th of September 2017, please check it out especially if you are interested in Microsoft Intune. cheers niall
  10. Hello, I've recently been given the task to oversee our SCCM 2012 R2 environment when the previous admin went off on leave. I have very little experience with SCCM but I had some device management experience. I've encountered a few problems. The one I'd like to discuss today, is that I do not know how to handle our Dell Venue 11 Pro 5130 and Venue 10 Pro 5055. They are tablets that have 64 bit architecture but can only run 32-bit Windows. If they are known devices there aren't any problems they pull the correct wim and the correct available Task Sequences appear, however when the device is unknown, the device downloads the correct 32-bit wim file but is being considered a 64-bit unknown device, and the task sequences that are deployed to the unknown x64 collection. So as a temporary fix I deployed the Venue task sequence to the unknown x64 collection, but now there are 2 boot images being deployed to the same collection, it's causing issues with some other x64 devices. I'm sorry if this isn't clear. Any help would be greatly appreciated, Thank you.
  11. Hi, I'm struggling to find a definative answer to a question. Is it possible to rebuild a machine via an OSD task sequence within SCCM 2012 R2? Is SCCM working correctly in that if I have previously built a machine via a task sequence, then try to rebuild that machine it does not see that same task sequence and therefore will not be able to be rebuilt? I have a sequence deployed to all unknown computers. The 1st time it builds fine, if I then try to rebuild, it will not see the task sequence. I am assuming as it's no longer an unknown computer. Part of the sequence places the computer in a specified OU, it seems that sometimes it will see the sequence, sometimes it will not. I am using a usb build key with not pxe boot server. Is it expected behaviour that you should delete the computer from SCCM and then rebuild, is there a work around to allow support staff who don't have access to SCCM to rebuild machines? Any help appreciated.
  12. Hello all. During OSD my task sequence is failing with error code 0x80004005 at the very end of "Apply Operating System". The attached smsts.log (smtsprobook) seems to indicate something funny going on with partitions? Test Systems: 1. HP Prodesk 400 G3 SFF 2. HP Probook 430 G3 History: I have created a task sequence for deploying Windows 7 Enterprise X64 w/ SP1. This task sequence works great for the HP Prodesk. No issues at all. Task Sequence Steps (in order): Capture Windows Settings Capture Network Settings Install Operating System Restart in Windows PE Format and Partition Disk Apply Operating System Apply Windows Settings The rest doesn't really matter since the task sequence is failing at "Apply Operating System" (On the HP Probook 430 G3) This issue only occurs on the Probook (laptop) and NOT the Prodesk (desktop). The way we are managing OSD here at my company is to have a "Golden" Task Sequence, then just copy that same task sequence for as many different model of systems we have and insert the corresponding driver package as well as rename the task sequence for whatever new model we discover we have or receive. So we received our new shipment of Probooks (laptops) and I did what I always do when we get a new model. I grabbed the Windows 7 drivers for it (Note: These systems come with Windows 10 installed. Our image is Windows 7 Enterprise x64 SP1.) and created/copied a task sequence for the new model by simply switching out whatever driver package was in the task sequence that I just copied with the correct package for that model (a lot of this is irrelevant since again, the task sequence is failing at "Apply Operating System" before it even tries to install drivers.) Things I Have Done: Made sure all content called for in the task sequence is on the DP Deployed the TS as Available (PXE,Media,Blah blah) to All Unknown Computers Read through the provided smsts.log and could not make sense of it. Seems error 0x80004005 is a "beat around the bush" error Created a task sequence from scratch then tested. Still same issue at the same place Thought maybe its an issue with my .wim but I dont think so as this has worked on some of our other models tested Came here for help I am at a total loss as of where to start to troubleshoot this error. Most of the info you will need to help asses the issue is probably contained in the log(CMTrace it). Please let me know of anything I left out that could help. Thank you! smtsprobook
  13. hello, I have a command line task sequence that creates a directory, copy the hokey software to the pc and then runs the exe. I have tested this command line on the actually pc by navigating to the directory using command prompt and running the below command and all works fine. The first two parts work fine but the last part just hangs on the users machine, any tips ? the command line i have in the task sequence is: cmd.exe "c:\drivers\hotkey\setup.exe" /SP- /VERYSILENT /NORESTART /SUPPRESSMSGBOXES any help would be appreciated
  14. Hey Guys / Niall - I am making an important deployment today and wanted at least one other to review it to ensure it's correct before enabling So for the next 2-3 weeks, I've been instructed to reboot thousands of workstations nightly with notification at 3:00am each morning. I already have a task sequence which executes a custom notification EXE which also offers delay options and more and once it exists then the system reboots successfully. When doing this previously, I was afraid that random reboots may occur so deployed the TS daily to be available the following morning at 2:59am, run at 3:00am, and end at 3:30am. So I don't have to remember to do this, I wanted to make a single advertisement. I considered doing the above and advertising via PowerShell to create a specific deployment per day - however - I don't think that's necessary. Below is the schedule I am planning have for the task sequence to run every Monday - Thursday night (actually 3:00am Tuesday - Friday) for two weeks. Look ok to you or see any chance of issues? Just making 100% sure Thanks!
  15. I've been using MDT for a few years now, up to and including MDT 2012 update 1. Now we've purchased SC2012, and I'm trying to rebuild the deployment setup in SCCM to do the same things I did before in MDT. It looks like there are several areas where things might work in a different way. Rather than trying to manually recreate the exact steps I had in MDT, I wanted to check first to see if there's a better way to accomplish the same goals in SCCM. The question of the moment is regarding bitlocker. In MDT, I had set customsettings.ini up with different sections for laptops and desktops, and depending on the IsLaptop variable, it would jump to whichever was appropriate. For laptops, I enabled bitlocker. For Desktops, I didn't. I created a new mdt task sequence in SCCM (sp1 beta), and I see that it has steps included for pre-provisioning bitlocker and enabling bitlocker, both are conditional on the existence of an OSDBitlockerMode variable. I don't know how that variable is set, but I'd like the same setup I had with MDT, such that bitlocker is only enabled on laptops. What's the best way to do this?
  16. Guys I am trying to figure out something that has happened in the last week that's never happened before. A bunch of our laptops received windows updates this past Tuesday out of the blue. When I go search in programs and features and look at the updates that were installed I can see these were patches we pushed out months ago. I know for a fact even on my own machine that I had a successful deployment (at least according to deployment monitoring) for the particular software update group. Is it possible for a client to get out of sync and send the wrong message to WSUS kicking off a reinstall? I've never seen anything like this. Any ideas would be appreciated.
  17. Hey guys, So I am rolling out SCCM and OSD. I am learning this totally from scratch, so it's kind of a long road. The tutorials and help guides in this forum have been a HUGE benefit, so let me thank you for that. My questions are more procedural at this point. I have SCCM set up, and I've followed every step in the SCCM 1511 deployment guides on the forum. I have my Windows 10 x64 image set up and have tested PXE booting, which works perfectly. So now...how do I go about this whole process for my help desk guys? I'm thinking right now I'm able to tell my help desk guys that I have deployed a clean image of Windows 10 x64, that will do some basic tasks (add to the domain, add to correct OU, enable .NET 3.5). They could start using this tomorrow. In the mean time, I will continue to work in the background on deploying each application we use. I envision that I can slowly roll out each one as I test it. Office 365 tomorrow, then our Loan Ops app, then another, etc. Is there a 'best practice' for setting up a build lab environment to test with, then migrate it to production once I'm happy? I have to imagine it's setting up a Device Collection specifically for testing, then create a test Task Sequence that I can use. Once I'm happy, is there a best way to push the new task sequence to production? Or do I just un-distribute the old Task Sequence to OSD Deploy and then distribute the new one? Sorry if I'm all over the place, I'm having a hard time knowing even exactly what I'm asking for. tl,dr: I want my help desk guys to be able to use what I've got ready so far with SCCM and OSD, and then push out new configurations as I test/implement them. Thanks in advance.
  18. Hi! I'm using a VBS script during OS deployment to set the AD computer description. But results are unpredictable at best (if you use numbers or gaps) Does someone has a suggestion for a good working solution ? script that I was testing : cscript.exe adcompdesc.vbs “%ComputerDescription%” dim Computerdn, strComputerName dim Args Set WshShell = WScript.CreateObject("WScript.Shell") '----Get Computer DN------ Set objADSysInfo = CreateObject("ADSystemInfo") ComputerDN = objADSysInfo.ComputerName strcomputerdn = "LDAP://" & computerDN Set objADSysInfo = Nothing '-----Read commandline--- Set args = WScript.Arguments strdesc = args(0) Addcompdesc strdesc Function addcompdesc(strPCdescription) Set objComputer = GetObject (strComputerDN) objComputer.Put "Description", strPCdescription objComputer.SetInfo end function
  19. Hello, We are running SCCM CB (1511) and I'm trying to push an package more than 70 workstations ,it's a mix of Win7 and Win10 . The package installs fine on the Win7 machines but not on the WIn10 workstation, the Deployment Status shows that it's "Waiting for a Service Window" I checked the execmgr.log and it shows : Succesfully raised SoftDistWaitingForServiceWindowEvent event for program AirMedia execmgr 8/8/2016 6:14:25 PM 6196 (0x1834) Execution Request for advert SE1200A5 package SE100121 program AirMedia state change from Ready to WaitingServiceWindow execmgr 8/8/2016 6:14:25 PM 6196 (0x1834) Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="SE100121",ProgramID="AirMedia", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l execmgr 8/8/2016 6:14:25 PM 6196 (0x1834) CServiceWindowEventHandler::Execute - Received SERVICEWINDOWEVENT : START Event execmgr 8/9/2016 9:27:02 AM 4080 (0x0FF0) CServiceWindowEventHandler::Execute - Received SERVICEWINDOWEVENT : END Event execmgr 8/9/2016 9:27:02 AM 7060 (0x1B94) CExecutionRequestManager::OnServiceWindowEvent for START execmgr 8/9/2016 9:27:03 AM 4080 (0x0FF0) Auto Install is set to false. Do Nothing. execmgr 8/9/2016 9:27:03 AM 4080 (0x0FF0) Any idea what might be the issue ?
  20. Hello All, I have a Powershell script that I use to create multiple Software Update Deployments and it works perfectly (well almost). The last piece I'm missing is automating the deadline date. Currently I just have it getting the current date and adding 5 days. I then go into each deployments properties and change the date/time to the desired info. I've been trying to work out automating this a little bit by adding a variable for a static date/time. I can then change this date (time will always be the same) to the desired info at script run. Below is what I've come up with so far. The -EnforcementDeadlineDay piece works on it own, in that it outputs the correct date with an incremented time. However once I put it in the full script i get the below errors. Any help is much appreciated. Cheers, Mike Script: # Monthly Deployment Date #$DeploymentDate = Get-Date -Format "yyyy-MM" $DeploymentDate = (Get-Date).AddDays(-30).ToString("yyyy-MM") $DeadlineDate = Get-Date -Month 08 -Day 07 -Year 2016 -Hour 17 -Minute 0 -Second 0 # Software Update Groups $SUPGroupName1 = "EN5 - EDC - Year 2013- ($DeploymentDate) Reference 1" $SUPGroupName2 = "EN5 - EDC - Year 2013+ ($DeploymentDate) Reference 2" #Load Configuration Manager PowerShell Module Import-module ($Env:SMS_ADMIN_UI_PATH.Substring(0,$Env:SMS_ADMIN_UI_PATH.Length-5) + '\ConfigurationManager.psd1') #Get SiteCode and set Powershell Drive $SiteCode = Get-PSDrive -PSProvider CMSITE Set-location $SiteCode":" # Create Standard Deployments (Group 1) $DeploymentName = "EN5 - PM Dev ($DeploymentDate) Reboot Deployment # 1" $DeploymentCount = 6 $Count = 0 1..$DeploymentCount | ForEach-Object { $Count++ Write-Progress -Activity "Creating Deployment Group 1" -Id 1 -Status "Running $($Count) / $($DeploymentCount)" -PercentComplete (($Count / $DeploymentCount) * 100) Start-CMSoftwareUpdateDeployment -SoftwareUpdateGroupName "$SUPGroupName1" -CollectionName "EN5 - PM - Deployment $Count (Lab)" -DeploymentName "$DeploymentName-$Count" -DeploymentType Required -VerbosityLevel AllMessages -TimeBasedOn LocalTime -DeploymentAvailableDay (Get-Date) -EnforcementDeadlineDay $DeadlineDate.ToLongDateString()$DeadlineDate.Addhours($Count).ToLongTimeString() -UserNotification HideAll -SoftwareInstallation $True -AllowRestart $True -RestartServer $False -RestartWorkstation $False -ProtectedType RemoteDistributionPoint -UnprotectedType UnprotectedDistributionPoint -GenerateSuccessAlert $False -DisableOperationsManagerAlert $False -GenerateOperationsManagerAlert $False -PersistOnWriteFilterDevice $False -UseBranchCache $False } Write-Progress -Activity "Creating Deployment Group 1" -Id 1 -Completed Errors: Start-CMSoftwareUpdateDeployment : A positional parameter cannot be found that accepts argument '6:00:00 PM'. At E:\scripts\EN5 - CreateDeployments - LAB.ps1:24 char:5 + Start-CMSoftwareUpdateDeployment -SoftwareUpdateGroupName "$SUPGroupName1" - ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidArgument: ( [Start-CMSoftwareUpdateDeployment], ParameterBindingException + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.ConfigurationManagement.Cmdlets.Sum.Commands.StartSoftwareUpdateDeploymentCommand Start-CMSoftwareUpdateDeployment : A positional parameter cannot be found that accepts argument '7:00:00 PM'. At E:\scripts\EN5 - CreateDeployments - LAB.ps1:24 char:5 + Start-CMSoftwareUpdateDeployment -SoftwareUpdateGroupName "$SUPGroupName1" - ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidArgument: ( [Start-CMSoftwareUpdateDeployment], ParameterBindingException + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.ConfigurationManagement.Cmdlets.Sum.Commands.StartSoftwareUpdateDeploymentCommand Start-CMSoftwareUpdateDeployment : A positional parameter cannot be found that accepts argument '8:00:00 PM'. At E:\scripts\EN5 - CreateDeployments - LAB.ps1:24 char:5 + Start-CMSoftwareUpdateDeployment -SoftwareUpdateGroupName "$SUPGroupName1" - ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidArgument: ( [Start-CMSoftwareUpdateDeployment], ParameterBindingException + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.ConfigurationManagement.Cmdlets.Sum.Commands.StartSoftwareUpdateDeploymentCommand Start-CMSoftwareUpdateDeployment : A positional parameter cannot be found that accepts argument '9:00:00 PM'. At E:\scripts\EN5 - CreateDeployments - LAB.ps1:24 char:5 + Start-CMSoftwareUpdateDeployment -SoftwareUpdateGroupName "$SUPGroupName1" - ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidArgument: ( [Start-CMSoftwareUpdateDeployment], ParameterBindingException + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.ConfigurationManagement.Cmdlets.Sum.Commands.StartSoftwareUpdateDeploymentCommand Start-CMSoftwareUpdateDeployment : A positional parameter cannot be found that accepts argument '10:00:00 PM'. At E:\scripts\EN5 - CreateDeployments - LAB.ps1:24 char:5 + Start-CMSoftwareUpdateDeployment -SoftwareUpdateGroupName "$SUPGroupName1" - ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidArgument: ( [Start-CMSoftwareUpdateDeployment], ParameterBindingException + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.ConfigurationManagement.Cmdlets.Sum.Commands.StartSoftwareUpdateDeploymentCommand Start-CMSoftwareUpdateDeployment : A positional parameter cannot be found that accepts argument '11:00:00 PM'. At E:\scripts\EN5 - CreateDeployments - LAB.ps1:24 char:5 + Start-CMSoftwareUpdateDeployment -SoftwareUpdateGroupName "$SUPGroupName1" - ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidArgument: ( [Start-CMSoftwareUpdateDeployment], ParameterBindingException + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.ConfigurationManagement.Cmdlets.Sum.Commands.StartSoftwareUpdateDeploymentCommand
  21. Hello, My company has decided to create and deploy the LTSB version of Windows 10 Enterprise instead of the CB version. Within the build process, we want to have applications populate the taskbar but every time we create the OS build and capture the OS and then test the deployment, the taskbar appears to empty which means that users will need to be instructed on finding the Internet Explorer icon, Windows Explorer Icon and have to drop the MS Office icons there. I might be missing something within the build process so I'm hoping there is a simple solution to creating a more customized desktop environment for users right from the image that gets put on their PCs.
  22. Hi all, I'm in the midst of learning the OSD process that's handled by SCCM. My task sequence is using the default steps in order to minimise confusion / issues. The problem I'm facing is that during the disk partitioning steps, the C: partition isn't being set as active, so when the TS steps through to deploying the OS, it cannot find an area to put it. The key areas of the log are pasted below, but I've attached the entire log just in case. Any guidance would be thoroughly appreciated. Thanks in advance. ==============================[ OSDDiskPart.exe ]============================== OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Command line: "osddiskpart.exe" OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Reading partition size info for partition 0 OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Remaining size before partition: 256052966400 OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) size units: SIZE_MB OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Set partition size: 367001600 OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Remaining size after partition 0: 255685964800 OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Set an environment variable for partitions 0-1 without drive letter OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Reading partition size info for partition 1 OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Remaining size before partition: 255685964800 OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) size units: SIZE_PERCENT OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) 100% size specified. OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Remaining size after partition 1: 0 OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Set an environment variable for partitions 0-2 with drive letter OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Checking volume 'C:' for BitLocker OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Volume 'C:' is on disk '0l' OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Volume 'C:' is fully decrypted OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Checking volume 'D:' for BitLocker OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Volume 'D:' is on disk '0l' OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Volume 'D:' is fully decrypted OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Checking volume 'X:' for BitLocker OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) S:\ ffffffff OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) R:\ ffffffff OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Q:\ ffffffff OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) P:\ ffffffff OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) O:\ ffffffff OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) N:\ ffffffff OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Diskpart: select disk 0 clean create partition Primary size=350 assign letter=S format quick fs=ntfs label="System Reserved" active create partition Primary assign rescan OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Executing diskpart script: select disk 0 clean create partition Primary size=350 assign letter=S format quick fs=ntfs label="System Reserved" active create partition Primary assign rescan OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Command line for extension .exe is "%1" %* OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Set command line: "X:\WINDOWS\system32\diskpart.exe" /s "X:\WINDOWS\TEMP\DiskPartScript.txt" OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Executing command line: "X:\WINDOWS\system32\diskpart.exe" /s "X:\WINDOWS\TEMP\DiskPartScript.txt" OSDDiskPart 02/06/2016 10:56:24 1176 (0x0498) Process completed with exit code 0 OSDDiskPart 02/06/2016 10:56:30 1176 (0x0498) Formatting partitions OSDDiskPart 02/06/2016 10:56:30 1176 (0x0498) Partition: 1 Primary OSDDiskPart 02/06/2016 10:56:30 1176 (0x0498) Partition: 2 Primary OSDDiskPart 02/06/2016 10:56:30 1176 (0x0498) Adding logical drive: C: OSDDiskPart 02/06/2016 10:56:30 1176 (0x0498) Adding logical drive: S: OSDDiskPart 02/06/2016 10:56:30 1176 (0x0498) Skipping non-local logical drive: X: OSDDiskPart 02/06/2016 10:56:30 1176 (0x0498) Formatting drive C: with NTFS filesystem, method quick OSDDiskPart 02/06/2016 10:56:30 1176 (0x0498) Start executing the command line: OSDApplyOS.exe /image:PPD00099,%OSDImageIndex% /runfromnet:False TSManager 02/06/2016 10:56:36 1100 (0x044C) !--------------------------------------------------------------------------------------------! TSManager 02/06/2016 10:56:36 1100 (0x044C) Expand a string: WinPE TSManager 02/06/2016 10:56:36 1100 (0x044C) Executing command line: OSDApplyOS.exe /image:PPD00099,%OSDImageIndex% /runfromnet:False TSManager 02/06/2016 10:56:36 1100 (0x044C) Command line for extension .exe is "%1" %* ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) Set command line: "OSDApplyOS.exe" /image:PPD00099,1 /runfromnet:False ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) Found run from net option: 0 ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) Not a data image ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) ApplyOSRetry: ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) TSLaunchMode: PXE ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) OSDUseAlreadyDeployedImage: FALSE ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) 'C:\' not a removable drive ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) Searching for next available volume: ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) Volume S:\ size is 350MB and less than 750MB ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) Volume C:\ is a valid target. ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) Found volume C:\ ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) Windows target partition is 0-2, driver letter is C:\ ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) !sSystemPart.empty(), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\diskvolume.cpp,130) ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) System partition not set ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) Unable to locate a bootable volume. Attempting to make C:\ bootable. ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) bBootDiskDefined == true, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installcommon.cpp,690) ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) Unable to find the system disk ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) MakeVolumeBootable( pszVolume ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installcommon.cpp,772) ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) Failed to make volume C:\ bootable. Please ensure that you have set an active partition on the boot disk before installing the operating system. Unspecified error (Error: 80004005; Source: Windows) ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) ConfigureBootVolume(targetVolume), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\applyos\applyos.cpp,499) ApplyOperatingSystem 02/06/2016 10:56:37 1484 (0x05CC) Process completed with exit code 2147500037 TSManager 02/06/2016 10:56:37 1100 (0x044C) !--------------------------------------------------------------------------------------------! TSManager 02/06/2016 10:56:37 1100 (0x044C) Failed to run the action: Apply Operating System. Unspecified error (Error: 80004005; Source: Windows) TSManager 02/06/2016 10:56:37 1100 (0x044C) smsts7.log
  23. Hi Guys, I've been building my Win10 image lately and for some reason SCCM refuses to complete any OSD Task Sequences successfully (on Win 10, or our old Win8.1 TS). It seems to be failing to setup the SCCM Client and then rebooting to a half built OS. smsts.log is here: https://pastee.org/7dkq5 I don't have a CCMSetup.log, it doesn't get that far. Any ideas? The key line that seems to stick out for me is: <![LOG[The action (Setup Windows and Configuration Manager) requested a retry]LOG]!><time="13:16:09.927-60" date="08-14-2015" component="TSManager" context="" type="1" thread="1260" file="engine.cxx:271"> <![LOG[Reboot to local harddisk]LOG]!><time="13:16:09.927-60" date="08-14-2015" component="TSManager" context="" type="1" thread="1260" file="engine.cxx:469"> I've been trying to work this out for the past few days now and I'm tearing my hair out Thanks!!
  24. Dear m8's, We got an Application deployed to a Usercolletion and to Devicecollection. As soon as we add any powershell-script based global condition to the requirements of the deploymenttype the application disappears from the Softwarecenter (Device-deployment) but it stays in the Softwarecatalog (User-deployment) If the Condition is Powershell and returns Stringit fails. if it is Powershell and returns boolean it works. if it is VBS and returns strin or boolean it works. For the Userdeployment it all works find the global condition script works as planed. But we can not deploy an application with such a global contition to devices. As an Example when we follow exactly this: http://www.kraftkennedy.com/creating-global-conditions-in-configuration-manager-2012/ We can not deploy an ap with that condition to a devicecollection only usercollection work. From the comments we see that others semm to have the same Problem. Any Ideas? Regards Aspi .... I can't believe it works as designed. Opened a supportcase at MS if we can not find a solution here i will report MS supportcase results here SystemCenter Configuration Manager 2012 SP2 CU4
  25. Hello, I definitely cannot understand the monitoring part !!!! Do you know why there are sometimes inconsistencies between the Deployment Status Summary that you can see in the Monitoring>Deployment tab and the Deployment Status Per Deployment Type that you can see by clicking on View Status ? (See file attached) I really love to know more about this because if we cannot monitor correctly the deployments we made, it would be difficult to know what to do in case of failure because we don't even know those ...
×
×
  • Create New...