$resulted_ds_list = Get-ChildItem -Path Registry::HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ -Name (I didn’t write the script – when I explained to the requester how it could be done, he was kind enough to write it for me.) $user_id_list = "CAINDBS2", "PTSBSTAR") To find them, I created a configuration baseline with the following script as the compliance setting. I feel like I am not tackling this issue in the best way.I received a request to find workstations that were using certain user names in ODBC data sources. Package the full audio driver separately - Run as TS Application in OS (rather than WinPE)Īdd a delay to TS - I don't like this as it "masks" the issueĬreate Packages instead of Applications for TS usage - I don't like this as it "masks" the issue Use Install Behaviour (new feature for me) -I read about this briefly and don't think this will work Moved Application Installs around the TS - produced better results but not 100% Maxx Audio Installer packaged separately - won't install separately by design I found some devices built pre-SCCM1806 upgrade and after inspecting Event Viewer these audio driver installs are consistently installing 3-4 mins before TS Applications begin so I have been lucky not to run into this issue before.Īs these audio driver installs are running at random times during the TS I need to control them so that I can be sure that the Application installs are not being done at the same time. I don't deploy these MSI's individually as part of the TS, they seem to be delayed from the driver pack install (done during WinPE) but I have not been able to work out what triggers the installs. Found this info in Event Viewer - Application Logs. In all failed cases these 2 installs are taking place right when the TS applications are installing, when a build is successful, these 2 installs are taking place before or after the TS applications. I am almost sure that the "other" installation causing the failure is coming from "Maxx Audio Installer (圆4).msi" and "SetupRAPCom.msi" which are part of the Dell audio driver installation.
Usually builds successfully on 2nd/3rd attempt Only ever fails on an application install (never any other part of the TS)Ĭould be any one of the application installs in TS (there are 10 that run consecutively, no restarts)Īpplication failed with exit code 1618 (Another installation running) Only affects certain models (mainly Latitude 7280, 7480) Shortly after the upgrade I started receiving reports of random OSD failures. Hello, I recently upgraded our SCCM environment from 1610 to 1806.
0 kommentar(er)
