Deploy Software on Organizational Unit - New Computers not automaticly added
Hi, when we deploy a Software/Configuration based on an OU it's working fine. But we have the Problem when new computers are added to the OU the deployment is not updated. Example: Software x will deployed on OU "Test" In Test is 1 Computer Software will
Manage on-going Process does not work
Hi, Software will be deployed althrough i configured a "manage on-going process" in the pre-deployment setting. In my test case i have installed Notepad++ Version 7.x and create a deployment of Version 8.4 with the pre-deployment setting "Wait for OUTLOOK
problem with partition number in operating system deployment
hello everyone I want to deploy an operating system with a central desktop, in my computer park I have machines with two partitions in the same hard disk, I just want to format the "C" partition and leave the "D" partition unformatted but when I want
Popup boxes with SelfService Portal after upgrade to 10.0.368
After upgrading to the latest version (10.0.368) our users are now getting 4 popup boxes when they open the SelfService portal. 1st box is a long Alpha Numeric string with an OK button 2nd box is "Zoho Corporation private Limited" with an Ok Button 3rd box is a repeat of the first 4th box is a repeat of the second After you click "ok" in the final box the Selfservice portal window does show up and is functional. The problem is our users think there's an issue and are all calling our service desk.
Dell Command Update - Command line interface
Trying to utilize Dell command update's CLI using desktop central. For the most part, it works. But.. results vary and are very inconsistent https://www.dell.com/support/article/us/en/19/sln311129/dell-command-update?lang=en https://topics-cdn.dell.com/pdf/command-update-v24_users-guide_en-us.pdf Here is configuration that works for x64 systems. normally packages fail in desktop central all the time when adding the /reboot switch, hence the post deployment activity. But the dells won't reboot at
Custom script (vbsscript) issue in Pre-Installation (Post-Installation) activities in Software Deployment
Hi I create vbs script, that should check on 64-bit machine installed program in both registry uninstall keys: 64-bit key HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall 32-bit key HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall When I run this script localy it's work correct. I place this script in pre-installation and post-installation activities. When DC Agent run this script it's work no correct - script check twice 32-bit registry key (( This is because the DC agent
Windows 10 Feature deployment via Self Service Portal
I'm attempting to configure Windows 10 1803 deployment to previous releases of Windows 10 via the Self Service Portal. I'm using the following command as a software deployment "\\DNSDomainName.local\DC Repository\Microsoft\Windows\10\1803\x64\Setup.exe" /ReflectDrivers "%programfiles%\McAfee\Endpoint Encryption\OSUpgrade" /auto upgrade /DynamicUpdate disable This command works fine manually but not via the Self Service Portal. Any ideas why. I just get a generic Windows Update warning '0x80070003
The remote server returned an error: (403) Forbidden
Can anyone provide advice on how I can resolve the following errors on my distribution server that is preventing Agents from connecting to it: Distribution Server Connectivity Info : DistributionLastAccessName, #SERVER-NAME#, 8021, http, Failed, The remote server returned an error: (403) Forbidden. DistributionServerName, #SERVER-NAME#, 8021, http, Failed, The remote server returned an error: (403) Forbidden. DistributionServerIPAddress, #SERVER-IP#, 8021, http, Failed, The remote server returned
Define Target by commas not work
In the new versions, define target by commas not work or not operating. I need this option, I have over 1000 computers and I can not make manually. in this way, DC It is not functional for me.
Java - Ready to execute
Hello everyone! I'm having problems with deploying Java to our company computers. We need of two Java versions, one is installed on D drive, one is installed on C drive. Newer version is installed first on C drive, then later older is installed on D drive. Problem is that, when we deploy Java to C drive, it sits and waits with "Ready to execute" status, but it is installing (Java first creates directory, installs some files in that directory, then at the end it cleans up that directory, registry