Hi Larry ,

Thanks for posting in the SOTI Central.

I would like to inform you that it is strongly advised to use the profile to make those changes on all the devices across the field/environment. It is easy to keep the track of changes made using the profile configurations.

However, you can perform the same action using the scripts if it is required for only one or two devices and it will not set to default until you send the script again with different value or "factory wipe" the device. The best practice is to use profiles to keep track of the changes made on the devices and payloads applied to the devices.

SCRIPT : sendinfo net.soti.action.surf BROWSERZOOMLEVEL VALUE

Also, if this post has helped you in solving your inquiry, I would request you to mark the particular comment as "is solution", so others may benefit from this information.

I ended up using a script that someone else has posted but was mainly posting about the "best approach" that most of you guys use.

We manage a small group of devices so I don't work in SOTI very much

Hi Larry ,

Following up on this thread, were you able to resolve the issue?

If yes, I would like to know what were the steps taken to resolve the issue and I can mark that "as a Solution.".

thank you very much for posting

I used the script approach but may revisit and set in profile since that's the best approach

working off memory:

created file sync rule and at first created a dummy.txt file which pointed to a file share

then in advance button added the script to set the browsers to preferred zoom level

later went back and deleted the dummy.txt file because I really didn't want the file pushed

to the devices even though it was just an empty txt file. even without the txt file it still runs the script, just set to run once,

if any new devices are added I can run the file sync manually