Config Mangler
-
Posts
157 -
Joined
-
Last visited
-
Days Won
3
Posts posted by Config Mangler
-
-
I have done a couple of these. We made sure automatic site assignment was not enabled and that site wide client push was not enabled.
We then managed the subnets from both servers and did a client push from the CB server to effectively migrate them to the new environment.
-
The "Install an existing image package" task sequence option pretty much does that in that order.
I would manage the subnets with SCCM then push the SCCM client to the W7 machines. Once they have inventoried the computer name will be in SCCM then you can deploy the task sequence to them.
Obviously import the drivers for the hardware and test first!
Don't see why you would get upgrade licence problems on a wipe n load.
-
You could look at using the pre-caching feature to get the content there ahead of time.
Note that if they are on WiFi the upgrade might not work. Mine wouldn't authenticate after the first reboot so did not continue the TS.
-
Is PXE broken for everything or just this model? Can you isolate it to a legacy / UEFI boot problem.
I don't use the DHCP scope options at all - just let SCCM respond on any subnet it manages.
So in the properties of the DP Role, PXE tab i have the first three options enabled.
-
I have the 830 G6. It doesn't do the audio drivers automatically in the task sequence from the imported INF drivers.
You need to run the setup program.
I added an application to the task sequence to install it. "setup.exe -s" worked.
-
Network problems.
Error 8007274d is connection could not be made ...
Error 80072ee7 is server name or address could not be resolved
So it doesn't join the domain, and everything else fails.
Have you got an IP address on the NIC not WiFI?
-
So you get some content some times? If it was something like boundaries you wouldn't anything.
Dodgy NIC driver on your physical machines then? Import latest NIC driver into WInPE.
-
Failing hash check is a corruption so dodgy network or corrupt content. You could try deleting the package and redistribute it again.
-
What version is SCCM? Think there was a hotfix for that.
-
80070002 is file not found.
Getting content hash value for reference package P010001E
Is that package distributed to the DP?
-
Never seen one with no tabs! Maybe re-import the boot image. Should be in \\servername\SMS_site\OSD\boot\x64
Could be Windows ADK not installed properly or wrong version - I would look at that too.
-
First have you got command support enabled on the boot image (F8). If not do that next.
If yes hit F8 as it's preparing network.
Do an IP config. Does it show a network driver and IP?
-
I don't specify the product key at all at that stage. Leave it blank is my suggestion!
-
Guessing you might need to push out the updated SCCM client to get the new feature.
-
Full WMI code for these is definitely "HP Compaq 8200 Elite SFF PC"
However I think you might have other problems with this model further down the line. They are ancient!
-
I don't see a problem with this. Install the MBAM client in your build or distribute after build time.
Set up MBAM server and associated group policy.
When it joins the domain you'll get group policy and the MBAM client will kick in and prompt the user for a PIN and encryption will start.
You need to add some REG keys to make this happen quickly
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\FVE\MDOPBitLockerManagement]
"ClientWakeupFrequency"=dword:00000001
"StatusReportingFrequency"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MBAM]
"NoStartupDelay"=dword:00000001 -
Not sure how mature peer cache and branch cache are. I'm also interested to see if anyone is making it work!
We use 1E Nomad for this purpose and have done for years. We have 1 main DP for 12,000 users because of this.
If you want to do an OSD at a slow site you build a master PC and ship it to that site. The clients can then pull everything from that PC and not go back to the DP.
-
No you can't patch it up a full release version. you need to use the in-place upgrade task sequence for existing machines or download the 1803 ISO and drop that into your wipe and load TS.
-
There's no upgrade path. You can only go LTSB -> LTSB
-
I've had that when driver source files have been removed so next time you do an update it can't find them and errors.
Look at the properties of the boot image and note what's under the drivers tab. Remove some or all of the drivers and update the boot image. If that's clean then import your NIC drivers again from source.
-
I never got the Surface 4 to PXE boot. I didn't take it much further as we don't have very many.
The later Surface Pro does PXE in exactly the same environment.
-
1
-
-
Caveat: Do not start deleting folders in SCCM without understanding the structure. If you are not short of disk space then leave it alone!
That said :-) if you wanted to move something large like an OS .WIM file, in:
Software Library | OS Images | Properties | Data Sources - note the existing path - copy the file to your new location - change the data source path to the new location then right-click Update Distribution Points - once you are happy it has replicated you can delete the file from the path you noted earlier.
-
Assuming you are booting the VM from an ISO, just recreate the ISO and it will have a new certificate.
Task sequences | Create Boot Media | Bootable Media | Site Based | CD/DVD Set - default is a year but you can make it longer
-
So in Operating System Images you should see PS100091 as the image ID for your 1803 WIM.
Click on content status then view status to see if there are any errors there. Guessing IIS is ok just giving an error as the content's not there.
OSD Deployment - PXE failing, Boot Media works
in System Center Configuration Manager (Current Branch)
Posted
There's an error in the log. Failed to copy the needed boot binaries from the boot image .....0035b.wim - have a google on that
Also later on you have
MAC ADDRESS D8:9E:F3:34:C1:18 Device is not in the database