Jump to content
DeployCentral

Ted Pruitt

Members
  • Content Count

    16
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Ted Pruitt

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I found GPO super unreliable. In most of my cases, it would install but the service wouldn't run so it would back out. I think the client is still a little buggy for GPO install at this stage. Also, to be fair, most of my issues were with Win 7 - since we've pushed out Win10 1809, it was less so, but on new systems, I just invoked the imaging process via PXE boot.
  2. Hey Devon - thanks for the clarification. I think you're right, I'll just recapture the whole image, it's pretty fast. Your advice, however, is slightly contradictory to some of the blog posts that talk about using the differencing wims as a way to have multiple version (e.g. base image, IT image, graphic artist image - each with different software being loaded.) My thought was that it seems silly to create a complete reimage for just (in this case) three little updates. But if that is what you recommend, that's fine. Also - this is the 1903 "LTSC" - NOT the "retail" version of Win10 1903 - so technically, it's 1809, they just named it based on the fact that they released it in March. SmartDeploy even labels it as 1809 in the images listings. Thanks
  3. So I have my base image of Win 10x64 1903 LTSC -- I pushed out a bunch of updates and instead of making a whole new image, i wanted to make a differential of just the updates so I didn't need to create a whole new image, figuring I would do this for every group of updates and then quarterly I would create a new whole image. When I pushed the image as a test, the test machine didn't have any of the updates. So perhaps I'm not understanding the concept. Do I have to push the DWM separately? Does it require making a deployment package and an answer file? Or is there maybe a special naming convention I missed? It appears to me that the computer I pushed to simply received the base image, nothing more. The documentation on differential imaging is pretty sparse. Also, as a future request, would it be possible to do something like they do with snapshots in VM-Ware - in which I could take the delta image and incorporate it into the final image, eliminating the need to recapture everything? Any help would be appreciated. Ted
  4. No - it doesn't install. I've opened the smartdeploy\source and the windows\temp folders during a push - what I observe is that the SPK gets copied into smartdeploy\source, then it unpacks itself into the windows\temp\smartdeploy\etc... but there is no evidence that it runs and nothing in any log file. It's like it just gives up. And I still think it's bizarre that your two packs work fine (that was before I disabled McAfee for the CLIENTSERVICE.EXE.)
  5. So just to update - I excluded CLIENTSERVICE.EXE from McAfee's access protection - now when I push an install, it ends with this: Log Name: Application Source: SmartDeploy Console/Client Service Date: 4/10/2019 10:52:03 AM Event ID: 20005 Task Category: None Level: Information Keywords: Classic User: N/A Computer: PCSPI-Z240-2QGG.senatedem.local Description: Application Pack, Run Command Task: ZoomClient-x64-1.0.0.0.spk Executable Location: C:\Windows\TEMP\SmartDeploy\Scratch\Application Manager\Zoom Client\Files\ZoomInstaller.exe Arguments: Return Value(s): -2 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="SmartDeploy Console/Client Service" /> <EventID Qualifiers="0">20005</EventID> <Level>4</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2019-04-10T15:52:03.212607200Z" /> <EventRecordID>61180</EventRecordID> <Channel>Application</Channel> <Computer>PCSPI-Z240-2QGG.senatedem.local</Computer> <Security /> </System> <EventData> <Data>Application Pack, Run Command Task: ZoomClient-x64-1.0.0.0.spk Executable Location: C:\Windows\TEMP\SmartDeploy\Scratch\Application Manager\Zoom Client\Files\ZoomInstaller.exe Arguments: Return Value(s): -2</Data> </EventData> </Event>
  6. Looking closer - it's McAfee blocking installation - but here's the weird thing - the two downloaded app packs I have (Filezilla & 7zip) work fine and aren't blocked - what the heck?
  7. Hey Glenn -- Yeah, I was just looking at that - appears to be a permissions issue: Log Name: Application Source: McAfee Endpoint Security Date: 4/10/2019 10:38:07 AM Event ID: 3 Task Category: None Level: Error Keywords: Classic User: SYSTEM Computer: PCSPI-Z240-2QGG.senatedem.local Description: EventID=1092 NT AUTHORITY\SYSTEM ran CLIENTSERVICE.EXE, which tried to access C:\WINDOWS\TEMP\SMARTDEPLOY\SCRATCH\APPLICATION MANAGER\ZOOM CLIENT\FILES, violating the rule "Prohibited", and was blocked. For information about how to respond to this event, see KB85494. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="McAfee Endpoint Security" /> <EventID Qualifiers="8192">3</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2019-04-10T15:38:07.889268000Z" /> <EventRecordID>61171</EventRecordID> <Channel>Application</Channel> <Computer>PCSPI-Z240-2QGG.senatedem.local</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data>EventID=1092 NT AUTHORITY\SYSTEM ran CLIENTSERVICE.EXE, which tried to access C:\WINDOWS\TEMP\SMARTDEPLOY\SCRATCH\APPLICATION MANAGER\ZOOM CLIENT\FILES, violating the rule "Prohibited", and was blocked. For information about how to respond to this event, see KB85494.</Data> </EventData> </Event>
  8. Trying to install the Zoom video conferencing client (see attached image) It tells me there is a deployment error but no real information. Any ideas where to start troubleshooting this? it's a simple .exe which I put in the app pack itself, no switches. It looks like the files get transferred, but it doesn't seem to know what to do with them. I've included the configuration screens as well.
  9. It's all good - just finished recreating them. Thanks Glenn - and thanks to your team for an AWESOME product. I recommend it to everyone I know in the industry.
  10. Never mind on the first question - I see that is the case. Very cool. Nice work guys!
  11. Also - while I have you - what is the new orange exclamation on my Deployment Packages screen - I'm assuming that indicates that there is an old client on board?
  12. Please clarify - there is some automatic upgrade that happens between the deployment server and the workstation? (Assuming the PC is on, of course)
  13. When a new version of SmartDeploy is released (like the one today - 2.0.3040) - is there a need to upgrade the client on your end-user PCs? And if so, how is that done?
  14. Well, that's the thing. Once I did the refresh - it was the same image. I don't know how you guys store the file names - if it's a database or a temp file or what - but it's like it saw the file name and kept the data from when it first started imaging. So quick answer is - yes, the image worked, I already deployed it after doing the "refresh" - so this was strictly something with the way SmartDeploy decides how to present the info in the console. To be fair to you guys - I am making LOTS of tweaks to my images and capturing them one after the other after each tweak. I think this was just a case of something stuck inside of however the files are displayed. I would've thought restarting the program would have cleared it up, but it didn't. I even restarted the machine itself. It wasn't until I right-clicked and hit refresh - and at that point the "unknown" disappeared and the correct name and file size replaced it. --T
  15. Found my own fix - replying here in case anyone else runs into it. Here seems to be the cause: Captured an image - for this example, let's call it "my_win10image_03072019" - I delete this image in the console - I capture and image from the same machine - and call it the same name "my_win10image_03072019" - in the console, this now shows up as "UNKNOWN" image with a bizarrely small file size. If you look at the file, it's the correct size. THE FIX: I right-clicked on the "unknown" image and selected "refresh" from the menu. It took 30-40 seconds or so, but it corrected and the image showed up with the correct name and the correct size. I'm deploying it now, just to be sure that it is, indeed, a good image. But I found no documentation on this error - so I thought this might help someone. I opened a ticket, so maybe they can include some kind of error handling that looks beyond the name and maybe looks at the creation date and updates the screen/database if the image is newer than what is stuck in the display list.
×
×
  • Create New...