🤘 9 reputation

GWhite

Standard

Joined: 1/15/2015

Last seen: 6/5/2019

Activity
  • I just took another look at your original collection screenshot. Change the Group Filter from Any to All. Any will return results for anything it finds with a value of 1, but not necessarily matching only the HiberbootEnabled key.

  • I was able to have only computers with HiberbootEnabled with a value of 1 added to the collection. I used the same scan profile as you and modified my collection slightly as shown below. Hopefully it works for you too.

    enter image description here

  • I too have a mix of Windows 7 and Windows 10, plus servers of course. I will do some testing and see if I can get to report correctly. While I do that, is your dynamic collection at the root or is it a sub-collection? I ask because I notice you do not have 'drill down from parent collection' selected and didn't know if that was skewing your results.

  • For the dynamic collection, instead of filtering for the path HKLM\CurrentControlSet\Control\Session Manager\Power\Hiberbootenabled, try this:

    enter image description here

  • In doing some more reading, it sounds like I can use the 'stop deploying to targets once they succeed' schedule option to prevent reinstalling the same version over and over. I will give this a try.

  • Question about Audo Download package and auto installation
  • Obtain screen resolution of user workstations
  • Hannebambel,

    If Vectorworks 2018 is in the name of the application, you can do it with a collection that shows ALL computers where 1) Application name equals Vectorworks 2018 and 2) Application name does not equal Vectorworks 2019.

    If the application name is just Vectorworks and you have to target by version number you can take the same approach show ALL computers where 1) Application equals Vectorworks, 2) Application version equals the 2018 version number and 3) Application version does not equal 2019 version number.

  • Please disregard this question, but I will leave posted in case it helps someone else.

    I have tested the setting 'send only when results change' on a schedule summary notification and it works just as I'd hoped. I set the schedule to run every 5 minutes and do not get notifications each time it runs successfully. I put a typo in to the ps file and when it failed I got a notification and then no more notifications while it continued to fail. Once I corrected the typo it was successful again and I got one notification alerting me to the success followed by no more notifications.

  • Notification only on deployment failure
  • When I originally set up my DFS namespace clients were pulling from any of the servers that hosted the DFS share and I had to configure the referal ordering method settings to 'Exclude targets outside of the client's site'. Unfortunately, I believe that if you do not have sites and subnets defined then changing the ordering method won't do any good because it's all on one site and there is no cost difference.

    Without defined subnets, what you might have to do would be to not have the repository on the DFS share and have packages defined per location; with each package set to push the file from the local server using the UNC path of server\share\ instead of pulling it from the UNC path. If you had 5 locations then you end up with 5 packages where the only difference was the source file path pointing to the local server. If you wanted to run the package against all locations at the same time you could create one overall package with each location specific package included as a nested package. It's not ideal, but sometimes we have to do what we have to do.

  • Thanks Patrick. I had linked to a specific collection, but the part about only running if found in the out of date group hadn't occurred to me.

  • Agreed. We have a shared folder at each site and use DFS to have a common namespace and replicate the files between sites. Repository is aimed at the unc of the DFS namespace and workstations at each site pull from their local server.

  • Patrick,

    Thank you for the information. I like the idea of not retrying on failure so that only deploys at night, but now that you mention it I recall reading somewhere else that Chrome will update while open without need to force close. If that is the case, then I don't think I'll worry about it too much.

    Regarding the edit, I will have one package set to install immediately to specific test computers and then the other package set to install to all other computers after several days delay. What I was trying to say was that I had come to the realization that the auto download package wasn't going to do anything on its own without me creating the necessary schedules to go along with the packages.

    Thanks again for your help.

  • Auto download and controlling installation time
  • We have WSUS and PDQ installed alongside each other on Server 2012 and haven't had any issues.

  • I figured it out. Somehow I overlooked that the Options tab Error Mode field was set to Continue instead of Stop Deployment with Error. Working as expected now.

  • That looks a lot easier than my script. I am learning more and more how much powershell can do, but am nowhere near fluent in it.

  • Colby,

    It's being run as a powershell step and I am running 15.3.0.0. The job itself shows a status of successful with no error.

    If I click on the 1 of 1 Steps link the job log there shows error:

     

  • We have a package that removed desktop shortcuts from all profiles. Our case might be a little different from yours in that our shortcuts were url shortcuts to a web based timekeeping system so they ended in .url instead of .lnk, but that concept should be the same.

    In my case the PDQ package is just calling a batch file. The batch file then iterates through all profiles looking for the shortcuts. In my batch file there are three different shortcuts it's looking for. Here is the script from the batch file:

    for /f %%a in ('dir /B /AD C:\Users') do (
        if exist "C:\Users\%%a\Desktop\Kronos Workforce Central.url" del /F /Q "C:\Users\%%a\Desktop\Kronos Workforce Central.url"
        if exist "C:\Users\%%a\Desktop\Quick TimeStamp.url" del /F /Q "C:\Users\%%a\Desktop\Quick TimeStamp.url"
        if exist "C:\Users\%%a\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\Quick TimeStamp.url" del /F /Q "C:\Users\%%a\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\Quick TimeStamp.url"
    )

    Not sure about the name variations you mention, but if there's a commonality, hopefully you can wildcard it.