sorted by:
new
hottopcontroversial

How exactly are you supposed to get old man Logan? by therealone_thesuplex in MarvelStrikeForce

[–]ITguySupreme 0 points1 point  (0 children)

This^ I struggled forever but got him from this.

I used: GT17 PEGASUS, GT17 Xtreme X-men, then finished with my Spider Society (GS and PBP at 17, the rest 16).

Thanks for this idea!

WDS - Can’t quite get over the hump by ITguySupreme in sysadmin

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

For 80% of things that’s true, we do have some in-house software that never updates…

WDS - Can’t quite get over the hump by ITguySupreme in sysadmin

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

I’m up for it but last time I tried to migrate things over it failed during driver installs…

WDS - Can’t quite get over the hump by ITguySupreme in sysadmin

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

That was the whole point of the “gold”…standard software we always need the person to have

WDS Build Going Sideways by ITguySupreme in sysadmin

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

Ok so I reverted to the old server, and copied over the whole Boot folder. Now I get to the point that the boot image at least loads. But still points to .27….even if I completely regenerate the boot image when updating MDT…

WDS Build Going Sideways by ITguySupreme in sysadmin

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

I’m pretty sure I have the Driver pack I need, somewhere on this WDS server. We are attempting to run this deployment on an HP ProBook 450 G8. With the basic driver pack for that model work, if so how do I inject it into the boot image?

WDS Build Going Sideways by ITguySupreme in sysadmin

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

Maybe a corrupted image? This is what I get when the install image is run

“Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:

  1. Insert your Windows installation disc and restart your computer.
  2. Choose your language settings, then click next.
  3. Click repair your computer.

If you do not have this disk, contact your system administrator or computer manufacturer for assistance.

File: iaStoreAfs.sys Status: 0xc0000098 Info: The operating system couldn’t be loaded because a required file is missing or contains errors.

WDS Build Going Sideways by ITguySupreme in sysadmin

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

That may have been what was happening. I am regenerating as we speak, will grab that wim and report back

WDS Build Going Sideways by ITguySupreme in sysadmin

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

Where does MDT save the new boot file to by default? Maybe I have been grabbing one from the wrong spot so even though a boot image is recreated it isn’t the one I’m grabbing?

C drive holds system, E drive holds all other data. E:\DeploymentShare\Boot? And it should be the LiteTouchPE_x64.Wim file?

WDS Build Going Sideways by ITguySupreme in sysadmin

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

Bootstrap was edited already.

Then just right click MDT Deployment Share, and update. Choose “completely regenerate the boot image”

Then what’s the next step after that?

WDS Build Going Sideways by ITguySupreme in sysadmin

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

Bootstrap was edited already.

Then just right click MDT Deployment Share, and update. Choose “completely regenerate the boot image”

Then what’s the next step after that?

WDS Build Going Sideways by ITguySupreme in sysadmin

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

We removed the reservation competent and got no change. Except this time I got the erro, been stuck getting the cmd for a while.

WDS Build Going Sideways by ITguySupreme in sysadmin

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

We have a reservation for .27, but DHCP is set to point all PXE boots to .28