Jump to content
DeployCentral

eburnett

Members
  • Content count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About eburnett

  • Rank
    Newbie
  1. My test failed - SD came back unable to find wim. So, basically it only takes the "differences" from then creates the file. This makes it useless for me if you have to recut the dwm everytime there is a change to the original, plus to make edits to the machine where the dwm was cut - might as well just keep it as a standard image for me - this is been my impression so far. On the upside, I just worked through my issues on my push install from client - couldn't tell if it was on the SD side or my answer key - the package wasn't being dropped, when I try to edit it defaults to D. I still get a warning box from the deploy page but it goes through ok, package and all. Yeah, we have to do adobe too, but we don't control our destiny - which is such a headache because we have no control over how the packages are created or when they will be updated. Also I see another password cluster**** down the line, with 365 - everyone came to us and said "don't you know my password?" with all the iterations I believe they will associate with old forgotten 365 passwords and - de ja vu. At least with 365 we had access to central management, not for us with Adobe.
  2. Custom Answer for Multiple Images

    Would be interesting to try, but doesn't seem practical. Seems you lose your indices either after setup or during capture - and it seems logical to lose your "baseplate" once you've authored significant changes to the OS (software and updates) - don't think there's a "real" way to make changes and put them back in, just minor stuff - (I think). SmartDeploy has been my sliced bread in this endeavor. But if you append to the wim (If you really, really, really had to) and refer back to the separate indicies, that would be interesting to know "what works". Re: bluescreens, finally fought through my BSOD on a HP built OEM disc, switched to volume license - newer Dells didn't care these older Optiplexs did. Rebuilt on proper media, "seems" to have fixed the issue Tried to find the best possible thread title to ask general questions about answer files: Would like to suggest a few changes, I would like to name machines by serial number, this actually means something to me (even though name will change) and I can do something with, replace WMI query AssetTag: SELECT SMBIOS.SerialNumber FROM Win32_SystemEnclosure SELECT SerialNumber FROM Win32_SystemEnclosure I prefer offline deployments - no dependencies and I can do them anywhere - however they are difficult to troubleshoot when bad media is involved. I noticed today I was having trouble with boot media, packages were not being installed on boot media (first selection). The option is available, but nothing is ever loaded (unless I choose offline boot media). When I opened up the xml I noticed this: <platform_pack>[ImageFolder]</platform_pack> This simply wont do - you are forced to enter network credentials in the Answer File wizard to map to the drive. Now if the image folder is on the network - you have to dump all your packages up there with your wim (which may be fine) - but for offline media - why not put it here where it fits the model: <platform_pack>[AnswerFolder]\z\</platform_pack> I don't like that sometimes my spanned wims are getting messed up. I find a lot of times it's because of the media, for UEFI boots (swm creation) is it possible to add a check integrity process? I'm assuming its doing a dism mount then splitting the wim Thanks
  3. I always kind of stayed away from this - kind of viewed it as a definitive demarcation point. ie - since I'm always getting updates I have to keep my base image fresh and I rather clone and setup (and update clones if need be) rather than make use of them - I see it as just another possible fail point. (If you have the space, why bother) I like the idea though, because if it were reliable then I only have to update one machine and the all the others that have different software setups would benefit from those updates, theory goes. What would help, is an explanation of how dwm works (the technical) in SmartDeploy, can you use them WDS? Would like to know how that works, thanks
  4. Capturing GUID partition table disk

    (Passing thru) - I believe (correct me if I'm wrong) as long as you boot UEFI and setup, you're golden. If you're trying to set up the disk for GPT, shift+f10 (diskpart, convert GPT) after language selection. I haven't checked GUIDs, but my boots show up as UEFI (didn't have to do anything fancy VM - just add programs and capture)
  5. Dell Latitude 7370 BSOD - Windows 7

    Awesome thanks
  6. Dell Latitude 7370 BSOD - Windows 7

    Will be interesting if you get around that m.2 - We have a unit that (I believe) the firmware is not updated causing the drive not to be recognized, and we have no plans going forward stepping back for this model to legacy OS. But on another unit, properly patched m.2 (was already updated) works like any other drive. My issue is with the package on SD site, something in the 7370 package is hosing my deploy, was hoping for a forum thread to report an issue with packages - Once I add the 7370 package I get stuck at getting ready screen, never finishes - without package, SD deploys.
  7. HP ProBook 645 BSOD

    Have (had) just worked through the same issue on Laptop - HP EliteBook Windows 7 Pro 850 G1. Weird thing was it never gave problems before (with this model) - coming here I thought "that seems reasonable" and maybe adopt a policy of not using dirty sticks "don't use SD sticks for VM" - reformatted media - created USB - that didn't work. Tried a different stick with a different reference image - no BSOD. Knowing for sure it's something on that stick it doesn't like - deleted the platform package and deployed - no BSOD. Had to download from the site a couple times, first time it said pp was corrupt - next deployment with pp was ok. If windows had a verbose mode during installation, that would be very helpful.
×