What's the advantage of IEM OSD from MDT alone

Usage and Config OSD
1

Hi All,

Whats the advantage of using IEM OSD from using MDT Alone? Thanks

2

Hi!

The main differences to me are:

  1. BigFix OSD has some great knowledge about drivers in your environment whereas MDT just does a blind driver pair.
  2. Very easy to do distributed (multi-office) OSD. MDT has share syncing but it kind of sucks and is very time consuming.
  3. BigFix can retain client settings on reimage
  4. BigFix allows for Zero-Touch Deployment (reimage remotely from a console) whereas normal MDT is Lite-Touch (Reimage sitting at the computer). Though you can customize MDT to be zero-touch.
  5. With BigFix OSD you are more likely to be doing the application installation with BigFix. We see a lot of MDT users doing application installations in MDT and having to produce content twice.
  6. BigFix OSD copies the deployment files locally to the endpoint whereas MDT typically runs off of a network share. This allows you to stage files for a mass-reimage without having peak network traffic during a mass reimaging.
1 Like
3

Hi Strawgate,

My client requirement is Zero touch deployment via PXE. I am unable to Automate below points.

1- How can we boot client machine from NIC (without pressing F12 key)
2- profile selection should be automatic
3- Language should be select automatic.

Please suggest.

Thanks in Advance.

4

1- in the OSD site there is the task “Force network boot” to boot a target via network (having the bes client running)
2- in the Bare Metal profile wizard there is the option Auto Deploy Timeout. In this case, you can also create a targeting rule to avoid a profile is automatically deployed to all targets that perform pxe boot.
3- when you create a Bare Metal profile, you can specify image locale and image keyboard locale in the wizard.

I hope this helps,
Viviana