Using the EUC Universal Sync Script in ControlUp

When using the EUC Universal Sync Script, make sure the "preview" Parameter is set to false in the cfg file to run the Sync script, and restart the monitor service for scheduling. The version on Github is the latest. The warning "Commit Changes?" is misleading but to assign False to the Preview parameter commit needs to be set to Yes. A bug in 8.8 related to Templates being empty was mentioned.

Read the entire ‘Using the EUC Universal Sync Script’ thread below:

In case you are using the EUC Universal Sync Script make sure you change the "preview" Parameter to false in the cfg file if you want to run the Sync script 🙂

Thanks

https://support.controlup.com/docs/euc-synchronization-with-universal-sync-script

Yeah Steve is working on how things are worded.

I was also in touch with @member. Maybe make sure that no double work is done 😄

Benjamin does the documentation part, Steve does the scripting side 🙂

You wrote „worded“ so I assumed you mean the documentation, that’s why I mentioned Benjamin 🙂

Neh also in the script itself it could get confusing at times 🙂

In what version? I have 0.22.29 and do not see that option.

I see it now. Is 0.22.29 the current one?Mine is set to true and seems to be working Correction. I see it says preview in the output.

Committing Changes:

Executing Folder Object Adds. Batch 1/1

Execution Time: PREVIEW MODE

Executing Computer Object Moves. Batch 1/1

Execution Time: PREVIEW MODE

Executing Folder Object Removal. Batch 1/1

Execution Time: PREVIEW MODE

-Msg Committing Changes took: 0.1562521 Seconds.

Changed to false and it looks better I agree with @member

It’s a bit confusing with the $Preview parameter. The caption "Commit Changes?" is misleading.

When using from the console, Commit Changes must be set to Yes to assign the Preview parameter False

still having issues implementing this. tried on 2 diff orgs today and the directions did not work. i think i got a method that works and will try again this week. I have 35 more orgs to do so I’ll get plenty of practice 😉

Let us know how it goes. And if you are still having trouble, you know how to reach us. 📧☎️💻😁

I used it in three orgs and two went flawless (after changing preview to false in cfg).

In one org I have an issue that the when the script runs as scheduled trigger, it doesnt work. If I ran it manually its doing great.

But theres lot security things involved and I think the monitors just doesnt have access to the API of Horizon, but we will figure out this one…

Check if the Horizon bits are available in Solve @member the universal sync script doesn’t connect directly with Horizon anymore but rather uses data that Solve would use with invoke-cuquery

So if the monitors don’t have active euc environment connections it also has no data to sync.Can someone confirm which is the current script? The older one has a newer version number.

We did another deploy today and did this:

Import script

Edit script

Finalize

Run script with commit=yes and mode=save

Run script with commit=yes and mode=run

All looked good. The existing folders were deleted and new ones created and populated with machines. Hey there Brian – I checked in with Steve and he suggested removing those versions and then downloading the latest version which you can find out our Github site – https://github.com/controlup/environment-scripts/tree/main/Environment_Synchronization_Scripts/UESS/EUCSync

@member that’s our cue 🙂

Thanks!

Is this still ‘beta’? When will it be available in the script store?

Neh we have plenty of customers already using it and by keeping it on Github fixes can be applied sooner. I think it’s already in the community library but it’s best to grab the latest from Github.

Trying it now. The published docs seems like it’s for a diff version. I’ll document my steps and results.

Unfortunately there is no versioning in the script itself. I will ask if this is on the roadmap…

We get a warning that the GitHub version of the sync script was made on a previous version of ControlUp. Other than that it works with these steps:

Version 0.22.29

Delete existing EUC Script

Delete the config file

\\####-monitor\C$\ProgramData\ControlUp\SyncScripts\Universal_EUC_Sync.cfg

Import Script

Edit script

Assigned to: MACHINE

OTHER MACHINE

####-Monitor

Shared Credentials: Domain\ControlupService acct

Finalize script

Do not share

Assign to ControlUP Admins

Right click on ####-Monitor

Run script action

EDIT: Folder Path: iWorkstation Desktops

EDIT Add Brokers: NO

Commit Changes: YES

Mode: Save

Run script again

Commit Changes: NO

Mode: Run

Check log file: \####-monitor\C$\ProgramData\ControlUp\SyncScripts\Logs

Create Trigger

That warning is perfectly normal if you import an XML, nothing to worry about.

Thanks!

The warning is there by default for any script made in an older version, just in case there was a breaking change. To be honest, I do not recall there ever having been a breaking change in the script engine 🙂

can you confirm what version i should see with the github xml?

I’m seeing 0.22.29 and 21.29

the xml on github is the latest as Steve makes them and he uploads it there\

Thx, It seems to show diff version numbers after i import it.

also getting this when trying to save the script action

NVM, i fixed it by restarting the monitor service.Uh, that’s something I saw at a customer with a different script running as automated action. Maybe sombody at ControlUp have an explanation why Templates are empty 😂

that’s a known bug, should be fixed in 8.8

what’s odd is my action was not set up to send an email.

I know but it’s related to that bug, I ran into the same issue

Continue reading and comment on the thread ‘Using the EUC Universal Sync Script in ControlUp’.  Not a member? Join Here!