I've created a .lnk that creates system restore points on demand. I want to run it "quietly" or "in the background" so my users do not see the cmd window.
I used the method listed below to create a .lnk file, I then used psexec to push that .lnk file to each workstation. I then added a command in the logon script for the users to run that shortcut on login. It's working perfectly, creating almost daily system restore points. I'd like to make the cmd window not pop up though, I know it only sits there for 10-15 seconds but my users are complaining.
I'm sure there's a simple argument or something I could add to the .lnk or possibly the logon batch file but i'm not as familiar with scripting this type of stuff as I should be.
http://www.windowscentral.com/how-create-system-restore-point-windows-10-simple-double-click
I'm sure there's a simple argument or something I could add to the .lnk or possibly the logon batch file but i'm not as familiar with scripting this type of stuff as I should be.
http://www.windowscentral.com/how-create-system-restore-point-windows-10-simple-double-click
ASKER
You don't know my users. I'd really like it just be silent, they won't really notice if their pc runs slightly slower for a few seconds at startup, but that big black box that shows up does. The box itself even says "Creating Restore Point" and we've emailed the users and let them know that's what we're doing. Still getting complaints. I just need to know if there's a way to run that exact function quietly.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks, Davis. I believe that will work, deploying it now after testing it on my own machine.
to do a fully hidden exe or bat file, make a something.vbs and put this in it
Set WshShell = CreateObject("WScript.Shell")
WshShell.Run chr(34) & "C:\foldername\filename.exe" & Chr(34), 0
Set WshShell = NothingASKER
Unfortunately, Aaron, i'm not allowed to use vbs scripts here. Thanks for your input though, my initial system restore process was a vbs script.
So, it's better to wait 10-15 seconds and not see anything? Won't users still complain? Especially if they don't know what's going on. How about putting a message in the window? At least they know what's happening.