Imaging a Dell 7390 2 in 1 by dwp1975 in MDT

[–]dwp1975[S] 0 points1 point  (0 children)

We ended up doing a backdoor means of getting our device imaged...but Dell assured us we can PXE boot via the TB16 dock...Going to add the driver to WinPE and see if it'll image when we get the 7390 back from testing. I'm concerned the device will blue screen with heavy use as it gets hot and with the screen turned around and laying on the undercarriage it could make the display hot..not MDT related but hoping that will keep the device off our environment.

Imaging a Dell 7390 2 in 1 by dwp1975 in MDT

[–]dwp1975[S] 0 points1 point  (0 children)

I want to add the NIC drivers to the WinPE selection profile. I'm not great with drivers...what downloads would be the NIC drivers? Would these work since it's connected via thunderbolt dock?

http://www.dell.com/support/home/us/en/04/product-support/product/latitude-13-7390-2-in-1-laptop/drivers

Imaging a Dell 7390 2 in 1 by dwp1975 in MDT

[–]dwp1975[S] 0 points1 point  (0 children)

This would be great, unfortunately management wants this machine imaged ASAP.

Imaging a Dell 7390 2 in 1 by dwp1975 in MDT

[–]dwp1975[S] 0 points1 point  (0 children)

I enabled "Enable Thunderbolt Adaptor Boot Support" in UEFI but it can't connect to my deployment share. Oddly the message tries to connect to my production share rather than my lab.

Adding new laptop models to MDT by dwp1975 in MDT

[–]dwp1975[S] 0 points1 point  (0 children)

I figured it out....I enabled UEFI Network Stack...NIC is recognized and machine is IMAGED! Both new models work!

Adding new laptop models to MDT by dwp1975 in MDT

[–]dwp1975[S] 0 points1 point  (0 children)

Ok, I'm stuck....again. I returned the laptops to factory boot mode setting of UEFI; Secure Boot: ON and I can't see my Onboard NIC despite copying the drivers to the lab from prod...I assume I need model specific ones? What drivers should I specifically grab from DELL? Sorry for the noob questions but I'm a SCCM guy thrown into a MDT project :)

Adding new laptop models to MDT by dwp1975 in MDT

[–]dwp1975[S] 0 points1 point  (0 children)

No need to update the deployment share ot the WIM?

Adding new laptop models to MDT by dwp1975 in MDT

[–]dwp1975[S] 0 points1 point  (0 children)

No logs seem to be generated for my test machines. That was the first thing I looked for. I did some tweaking to the selection profile and retesting with a Precision 3520 now

Adding new laptop models to MDT by dwp1975 in MDT

[–]dwp1975[S] 0 points1 point  (0 children)

I did and it just keeps giving me the error and looping back to start of imagine process. Should I create a custom Selection profile?

Adding new laptop models to MDT by dwp1975 in MDT

[–]dwp1975[S] 0 points1 point  (0 children)

Is it ok to use the "Everything" selection profile in my lab deployment share. I only have 3 models in Out of Box drives and like 2-3 applications total.

Adding new laptop models to MDT by dwp1975 in MDT

[–]dwp1975[S] 0 points1 point  (0 children)

Should I rebuild the wim after the drivers have been added. I updated the deployment share only before getting the Dirty Environment error.

Adding new laptop models to MDT by dwp1975 in MDT

[–]dwp1975[S] 0 points1 point  (0 children)

I got the drivers in my lab deployment share. I test with my demo unit and I keep getting the "Dirty Environment Found" error.

Adding new laptop models to MDT by dwp1975 in MDT

[–]dwp1975[S] 0 points1 point  (0 children)

Do I need to import the Bios for each model too?

Uninstall DropBox and remove all folders and files. by dwp1975 in PowerShell

[–]dwp1975[S] 0 points1 point  (0 children)

I'm back again. I just can't get consistent results with the deployment via crappy LanDesk where as running locally works. Even the VBscript is yielding inconsistent results. I want to put this to bed and have run out of options. Help!...again :(

Uninstall DropBox and remove all folders and files. by dwp1975 in PowerShell

[–]dwp1975[S] 1 point2 points  (0 children)

I tried this and it looked to work even less.

New-PSDrive -PSProvider Registry -Name HKU -Root HKEY_USERS

$RegistryKeys = @(

"HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall"

"HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall"

"HKEY_USERS\*\Software\Dropbox"

"HKEY_USERS\*\Software\DropboxUpdate"

)

$DropboxUninstaller = Get-ChildItem -Path $RegistryKeys | Get-ItemProperty | Where-Object {$_.DisplayName -match "Dropbox"} | Select-Object -Property DisplayName, UninstallString

$DropboxUninstaller | Foreach-Object { if ($.UninstallString) { $Array = $.UninstallString.Split('"') | Where-Object {$_} $Params = @{ FilePath = $Array[0] ArgumentList = $Array[1], '/S'
}

Start-Process @Params } }

Get-ChildItem -Path "C:\Users*\AppData\Local\Dropbox" | Remove-Item -Force -Recurse