Hi, by copying over a new Sylink.xml file to an old SEP client to put it onto a new SEP server, is this causing the client to reboot? I don't want it to update the client to the new version, nor do I want it to reboot it! Is there a flag I can pass with Sylinkdrop.exe that will tell the client not to do this?
I wrote a batch script that will copy 3 files (SylinkDrop.exe, Sylink.xml file, and SylinkDropCommand.xml) to a remote client and execute the SylinkDrop.exe file using PSEXEC.
I've taken a couple of test clients and run the batch file on them and it works just fine and I can see the client on the new SEP server, but it wants to upgrade the software to the latest version and we don't want it to do this. How can I prevent this from happening until we manually send a command to reboot?
Thanks,
Dan