Jump to content


2SR82

Established Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About 2SR82

  • Rank
    Newbie
  1. The resulting Client Settings are correct in my case. They simply seems not to get applied correctly. The different sets of client settings are a result of different locations with different permissions and so on. I will try to "reorganize" the client settings at sometime. At the moment unfortunately I have no time to focus on that. I can live with the problem for now because only a few clients affected in our network.
  2. Unfortunately no final solution, but I recognized that it has something to do with the client settings. On some clients the "Remote Tools" Settings simply seems not to be applied correctly. The Group "ConfigMgr Remote Control Users" under Local Users and Groups is missing on the affected clients. That seems to be the reason why it's not possible to connect to the devices. As a workaround, in that case I simply add the device to an collection with different client settings (different Remote Tools Settings) and force the client to download the Computer Policy. After this the "ConfigMgr Remote Control Users" should be automatically created. Now you can remove the client from the temporary collection and force Policy refresh again to get the correct settings. It's not so nice but the workaround is working, at least for me. I'm still not sure why this is happening. I think in our case only "reinstalled" devices (which already was connected to SCCM) are affected, new devices are always working. We have about 20 different "client settings" for different locations and so on. I'm not sure if SCCM has a bug/problem to handle this number of different settings. hope that helps some of you..
  3. Not in my case. For me only some Clients affected. All of them (working and not working) are in the same OUs with same Win 10 OS. So they also have the same policies. At the moment I'm investigating the Logs of two devices and hope to finde some differences/problems.
  4. Hello, thanks for your help! Meanwhile I have found a solution for my Problem here: https://social.technet.microsoft.com/Forums/en-US/0e831d5e-b607-4cd5-8c9f-0e94eaca8d8f/deploying-java-8-u-40-with-powershell-application-deployment-toolkit-works-fine-locally-but-fails?forum=configmanagerapps Seems that it has something to do with the AppData Environment Variable. I could easily solve the problem with copying the "java.settings.cfg" described in the last Post for now. We will see how long it works until Oracle will change something again.
  5. Hello, I'm using the very good script from "http://psappdeploytoolkit.com/"since about 2 years now. Never had big problems with it, but now I have the following strange behavior. Not sure if it's SCCM or Script related, so I will ask on both places ;-) I have a strange behavior trying to deploy Java 8 Update 91/92. Until now I had used the Toolkit for deploying the extracted MSIs of the Java Installer without Problems. Since the last 2 or 3 releases, Oracle seems to have changed something in the MSI (64bit) so that it shows an error when trying to install and I’m forced now to use there EXE Installer. I’m executing the Installer with the following line: Execute-Process -FilePath "$myEXENameX86" -Arguments "/s AUTO_UPDATE=0 REBOOT=0 SPONSORS=0 /L `"$env:windir\Logs\Software\$myEXENameX86.log`"" -WaitForMsiExec -PassThru If I execute the script by right click and “run as Administrator”, everything runs fine and the Installer finishes successfull. But if I now create a package from this script and deploy it with our SCCM Infrastructur (as Application) the Script starts fine, executing the EXE, getting back the Exit Code 0 but nothing is installed! part of the LOG: [Installation] :: [jre-8u92-windows-i586.exe] successfully resolved to fully qualified path [C:\WINDOWS\ccmcache\f\Files\jre-8u92-windows-i586.exe]. Execute-Process 11.07.2016 10:09:33 3700 (0x0E74) [Installation] :: Check to see if mutex [Global\_MSIExecute] is available. Wait up to [10 minute(s)] for the mutex to become available. Test-IsMutexAvailable 11.07.2016 10:09:33 3700 (0x0E74) [Installation] :: Mutex [Global\_MSIExecute] is available for an exclusive lock. Test-IsMutexAvailable 11.07.2016 10:09:33 3700 (0x0E74) [Installation] :: Working Directory is [C:\WINDOWS\ccmcache\f\Files]. Execute-Process 11.07.2016 10:09:34 3700 (0x0E74) [Installation] :: Executing [C:\WINDOWS\ccmcache\f\Files\jre-8u92-windows-i586.exe /s AUTO_UPDATE=0 REBOOT=0 SPONSORS=0 /L "C:\WINDOWS\Logs\Software\jre-8u92-windows-i586.exe.log"]... Execute-Process 11.07.2016 10:09:34 3700 (0x0E74) [Installation] :: Execution completed with exit code [0]. Execute-Process 11.07.2016 10:10:08 3700 (0x0E74) The Installer of Java even didn’t create a own Logfile if I start the Script over the SCCM deployment. This is independent if I start the Application-Installation from the Application Catalog (as User) or deploy it directly to the System (Device). If I’m now going to the local Cache folder of the Application and start it again via Right Click > run as Admin, everything installs fine again. (perhaps I had a similar issue with the Adobe Acrobat Installer a few weeks ago, there was a missing IE-Plugin after the Installation, but I hadn’t verified it now.) I’m not sure if this is a Problem with the Toolkit or with SCCM. We are using Version 1511 (5.0.8325.1000) of SCCM and PSADT-Script Version 3.6.8. Perhaps anyone have a hint for me what I can try to solve. I can’t imagine to work without the toolkit Thanks for any help!
  6. Hi, is it possible to build a collection based on the content of a cfg/txt file? i have an program which can be used with different licences. the basic data of the program are the same. it only differs in one single config file where stands a path to a different file on a server. Is there a way to analyse the content of a specific line in that file and build collections based on that content?
  7. We have an additional WSUS Server running in the Network. And the Site Server has an End Point Protection Role installed. Could that be a Problem?? BOOT.WIM's are distributed (multiple times) to the DP.
  8. Hi, we are using SCCM 2007 quite a while now and at the moment we preparing to move to SCCM 2012. We have installed a new Site Server and building new packages at the moment. (Many things on the 2007 was not structured very well and there many packages very crappy so we decide to build most things completely new.) ATM we have only one Distribiution Point (in 1 Group) at the Site Server. PXE is enabled. Boot Image is checked "Deploy this Boot-Image from the PXE Service Point" Boot Image, Operatingsystem Image, SCCM Client, Driver are all distributed to the DP. Tasksequence is distributed to the collection - configured as "Make available to boot media and PXE" If I now boot an client into PXE it connects to the server and abort with: "Contacting Server: 172.16.11.14 TFTP Download: smsboot\x64\abortpxe.com PXE Boot aborted. Booting to next device... PXE-M0F: Extiting Intel Boot Agent." The SMSPXE.log on Server says following: Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777240" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply> SMSPXE 30.09.2013 15:41:46 2844 (0x0B1C) 00:50:56:21:8F:56, 690F4D56-2D6D-7408-0CA0-E0479E5C071C: device is in the database. SMSPXE 30.09.2013 15:41:46 2844 (0x0B1C) Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777240" ServerName="" ServerRemoteName=""><Machine><ClientID>GUID:14E36B1F-80E9-436A-B9C6-C01E01E626D4</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CM020003" OfferIDTime="30.09.2013 14:44:00" PkgID="CM00001F" PackageVersion="" PackagePath="http://XXXXXXX.XXXXXXXXXXXXX.com/SMS_DP_SMSPKG$/CM000028" BootImageID="CM000028" Mandatory="1"/></ClientIDReply> SMSPXE 30.09.2013 15:41:46 2844 (0x0B1C) 00:50:56:21:8F:56, 690F4D56-2D6D-7408-0CA0-E0479E5C071C: using advertisement CM020003 SMSPXE 30.09.2013 15:41:46 2844 (0x0B1C) so it seems, that the the Client can't boot/load the Boot-Image. After this lines nothing more is logged into the SMSPXE. Unfortunately i have no idea where or in what log-file i can look for following errors. Additional i have tested the following things: - deploy the task sequence to unknown computers instead of a special collection - created new boot images from "\Program Files\Microsoft Configuration Manager\OSD\boot" as well as from "\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment" Always the same problem. I have tested this with 2 Clients (1 VM and 1 Dell Laptop). Same Error on both. Can anybody give me a hint what the Problem could be or where i can look for erros that occur. Greetings
×
×
  • Create New...