Hi Alex,
aha, könnte mir vorstellen, dass Patchlink ein Office 365-Update am Client triggert.
Das würde allerdings bedeuten, dass die Quellen von jedem einzelnen Client heruntergeladen werden und nicht 1x für alle.
Wenn du dir das anschaust, sag bitte nochmal Bescheid was raus kommt - das interessiert sicher auch noch ein paar andere hier...
Ciao
Klaus
thankyou very much Andi
Hi
The switch between sessions, is very long on a CV31 Ce7.0. Version TE 7.3.296. I clocked, and it's over 30 seconds each time. Despite the disabling of network support, the problem remains unresolved. An idea ?
CV31 + SR61B + Wavelink TelnetCE 7.3.256- 4 VT sessions.
PS: I tried the universal version, and no problem switch but problems reading Bluetooth SR61B scanner.
see the video real time attached.
Thanks fo Help
Hallo,
hat hier jemand schon einmal GoToMeeting erfolgreich als eScript DSM Paket paketiert? Ich habe bereits mehrere Installationsvarianten versucht - leider alle ohne Erfolg.
Installiert man die Multi MSi mit MSIInstallProduct so erscheinen auf den Client mehrere Windows PopUp Fenster mit "Erkennung interaktiver Dienste. Von einem auf diesem Computer ausgeführten Programm wird versucht, eine Meldung anzuzeigen".
Möchte man die MSI mit den Silent Parametern installiert so erscheint im DSM Log die Fehlermeldung: "Failure while installing MSI package. MSI returned: (1639) Invalid command line argument. Consult the Windows Installer SDK for detailed command line help."
Installiert man diese MSI über CMD mit msiexec und genau den selben Parametern funktioniert die Installation einwandfrei. Die Installation des GoToOpener funktioniert - das GoToMeeting läuft allerdings immer in einen TimeOut bzw. bringt diese Windows Popups.
Laut Google Foreneinträge + Citrix Installation Guide PDF lässt sich das GoToMeeting nur sauber über Gruppenrichtlinien für alle User des PCs verteilen. Hat das schon jemand über DSM für alle Benutzer des PCs hinbekommen?
Anbei die Installationsfiles (Multi Build MSI): Install via MSI (Windows) - gleiches Problem aber ebenso mit der Single Build Variante.
Hier noch die Log Varianten meiner verschiedenen Tests:
Variante 1:
| 15:08:54.591 2 | -> RunAsEx('C:\Windows\system32\msiexec.exe','/i C:\Program Files (x86)\Common Files\enteo\RepositoryCache\67963\rev\7\Extern\G2MSetup8.12-8.20_IT.msi /quiet','',*****,'15','_return',raUseSisAccount+WaitForExecution+raLogonWithProfile+raHideWindow+UndoneContinueParentScript)/TS |
| 15:08:54.627 2 | clnexcln.dll: Security warning: UAC seems to be disabled for dsm_run. |
| 15:08:54.684 2 | xniTools: Created process with process id 5136 |
| 15:08:54.684 1 | xniTools: Waiting for process 15 minutes... |
| 15:23:54.763 2 | xniTools: Process execution timed out. |
| 15:23:54.763 1 | xniTools: Setting exit code variable '_return' to 'TimeOut' |
| 15:23:54.765 1 | Evaluating condition "not __return_='0'" | |
| 15:23:54.767 2 | Condition TRUE | -> entering IF part |
| 15:23:54.769 2 | -> ExitProcEx(Failed,'Installation mit Fehlercode TimeOut fehlgeschlagen') |
| 15:23:54.770 2 | New last error from script command is 1627 (0x0000065b) |
| 15:23:54.770 2 | Resolved new last error from script command is: Beim Ausführen der Funktion ist ein Fehler aufgetreten. |
| 15:23:54.771 2 | xniFPS: '{4CF25162-CBFE-4ED5-9640-00557395EA58}' is installed |
| 15:23:54.772 2 | FPS.dll: Closing the file package '\\?\C:\Program Files (x86)\Common Files\enteo\RepositoryCache\67963\rev\7\' |
Variante 2:
| 13:21:09.589 2 | -> MSIInstallProduct('C:\Program Files (x86)\Common Files\enteo\RepositoryCache\67963\rev\5\Extern$\G2MSetup8.12-8.20_IT.msi','NORMAL',MsiInstMach) ... /TS |
| 13:21:09.601 1 | xniMSI: Status verification of C:\Program Files (x86)\Common Files\enteo\RepositoryCache\67963\rev\5\Extern$\G2MSetup8.12-8.20_IT.msi... |
| 13:21:09.605 1 | xniMSI: Package verified OK. |
| 13:21:09.628 2 | xniMSI: Product info: GoToMeeting 7638-8199 IT Installer 8.20.8199 |
| 13:21:09.628 2 | xniMSI: Product GUID: {E16AC76E-78E5-4421-9CF9-0678EA638178} |
| 13:21:09.629 2 | xniMSI: Current install state: INSTALLSTATE_UNKNOWN |
| 13:21:09.675 1 | xniMSI: MSI logging enabled. LogLevel is NORMAL (0x00001bc7). LogFile is C:\Program Files (x86)\Common Files\enteo\NiLogs\MSI\NiMsiInst1519129269[GoToMeeting 7638-8199 IT Installer].log |
| 13:21:09.676 2 | xniMSI: MSI settings: Advertise: None (FullInstall) ~ Install: per machine ~ |
| 13:21:09.676 2 | xniMSI: Install state of package {E16AC76E-78E5-4421-9CF9-0678EA638178} : INSTALLSTATE_UNKNOWN |
| 13:21:09.676 1 | xniMSI: Starting installation through MSI... |
| 13:21:09.982 E | Warning (Module:xniMSI, Severity:0x03): an unnamed file contains an incorrect path. |
| 13:21:09.983 E | Error (Module:xniMSI, Severity:0x0b): Failure while installing MSI package. MSI returned: (1639) Invalid command line argument. Consult the Windows Installer SDK for detailed command line help. |
| 13:21:09.983 2 | Messagebox suppressed (No output allowed), output is written to the log files |
| 13:21:09.983 2 | MsgBox: [Failure while installing MSI package. MSI returned: (1639) Invalid command line argument. Consult the Windows Installer SDK for detailed command line help. |
Installation wird beendet.]
| 13:21:09.986 2 | New last error from script command is 2147614729 (0x80020009) |
| 13:21:09.986 2 | Resolved new last error from script command is: Ausnahmefehler aufgetreten. |
| 13:21:09.986 2 | Execution terminated on error |
| 13:21:09.987 2 | xniFPS: '{4CF25162-CBFE-4ED5-9640-00557395EA58}' is installed |
| 13:21:09.987 2 | FPS.dll: Closing the file package '\\?\C:\Program Files (x86)\Common Files\enteo\RepositoryCache\67963\rev\5\'. |
| 13:21:09.988 2 | ---->Installation of Go2Meeting has not completed on exit. |
Variante 3:
| 08:41:31.646 2 | -> MSIInstallProduct('C:\Program Files (x86)\Common Files\enteo\RepositoryCache\67963\rev\8\Extern$\GoToOpenerMultiUser.msi','NORMAL',MsiInstMach) ... /TS |
| 08:41:31.658 1 | xniMSI: Status verification of C:\Program Files (x86)\Common Files\enteo\RepositoryCache\67963\rev\8\Extern$\GoToOpenerMultiUser.msi... |
| 08:41:31.665 1 | xniMSI: Package verified OK. |
| 08:41:31.700 2 | xniMSI: Product info: GoTo Opener (Multi User) 1.0.473 |
| 08:41:31.700 2 | xniMSI: Product GUID: {4944A7A3-37B0-47EB-8DC3-7BA2801753BA} |
| 08:41:31.701 2 | xniMSI: Current install state: INSTALLSTATE_DEFAULT |
| 08:41:31.760 1 | xniMSI: MSI logging enabled. LogLevel is NORMAL (0x00001bc7). LogFile is C:\Program Files (x86)\Common Files\enteo\NiLogs\MSI\NiMsiInst1519371691[GoTo Opener (Multi User)].log |
| 08:41:31.760 2 | xniMSI: MSI settings: Advertise: None (FullInstall) ~ Install: per machine ~ |
| 08:41:31.761 2 | xniMSI: Install state of package {4944A7A3-37B0-47EB-8DC3-7BA2801753BA} : INSTALLSTATE_DEFAULT |
| 08:41:31.761 1 | xniMSI: Starting installation through MSI... |
| 08:41:34.577 2 | xniMSI: Install state of package {4944A7A3-37B0-47EB-8DC3-7BA2801753BA} : INSTALLSTATE_DEFAULT |
| 08:41:34.577 1 | xniMSI: Writing package ID '67963', revision 'R8', repository '66031' to registry |
| 08:41:34.577 2 | xniMSI: Successfully installed GoTo Opener (Multi User) 1.0.473. |
| 08:41:34.578 2 | -> RunAsEx('C:\Windows\system32\cmd.exe','msiexec /i C:\Program Files (x86)\Common Files\enteo\RepositoryCache\67963\rev\8\Extern\G2MSetup8.12-8.20_IT.msi /quiet','',*****,'15','_return',raUseSisAccount+WaitForExecution+raLogonWithProfile+raHideWindow+UndoneContinueParentScript)/TS |
| 08:41:34.626 2 | clnexcln.dll: Security warning: UAC seems to be disabled for dsm_run. |
| 08:41:34.711 2 | xniTools: Created process with process id 3452 |
| 08:41:34.711 1 | xniTools: Waiting for process 15 minutes... |
| 08:56:34.774 2 | xniTools: Process execution timed out. |
| 08:56:34.774 1 | xniTools: Setting exit code variable '_return' to 'TimeOut' |
| 08:56:34.775 1 | Evaluating condition "not __return_='0'" | |
| 08:56:34.777 2 | Condition TRUE | -> entering IF part |
| 08:56:34.777 2 | -> ExitProcEx(Failed,'Installation mit Fehlercode TimeOut fehlgeschlagen') |
Variante 4:
| 10:01:57.884 2 | -> MSIInstallProduct('C:\Program Files (x86)\Common Files\enteo\RepositoryCache\67963\rev\9\Extern$\GoToOpenerMultiUser.msi','NORMAL',MsiInstMach) ... /TS |
| 10:01:57.896 1 | xniMSI: Status verification of C:\Program Files (x86)\Common Files\enteo\RepositoryCache\67963\rev\9\Extern$\GoToOpenerMultiUser.msi... |
| 10:01:57.900 1 | xniMSI: Package verified OK. |
| 10:01:57.927 2 | xniMSI: Product info: GoTo Opener (Multi User) 1.0.473 |
| 10:01:57.927 2 | xniMSI: Product GUID: {4944A7A3-37B0-47EB-8DC3-7BA2801753BA} |
| 10:01:57.928 2 | xniMSI: Current install state: INSTALLSTATE_DEFAULT |
| 10:01:57.969 1 | xniMSI: MSI logging enabled. LogLevel is NORMAL (0x00001bc7). LogFile is C:\Program Files (x86)\Common Files\enteo\NiLogs\MSI\NiMsiInst1519376517[GoTo Opener (Multi User)].log |
| 10:01:57.970 2 | xniMSI: MSI settings: Advertise: None (FullInstall) ~ Install: per machine ~ |
| 10:01:57.970 2 | xniMSI: Install state of package {4944A7A3-37B0-47EB-8DC3-7BA2801753BA} : INSTALLSTATE_DEFAULT |
| 10:01:57.971 1 | xniMSI: Starting installation through MSI... |
| 10:02:00.159 2 | xniMSI: Install state of package {4944A7A3-37B0-47EB-8DC3-7BA2801753BA} : INSTALLSTATE_DEFAULT |
| 10:02:00.159 1 | xniMSI: Writing package ID '67963', revision 'R9', repository '66031' to registry |
| 10:02:00.159 2 | xniMSI: Successfully installed GoTo Opener (Multi User) 1.0.473. |
| 10:02:00.161 2 | -> RunAsEx('C:\Windows\system32\msiexec.exe','/i C:\Program Files (x86)\Common Files\enteo\RepositoryCache\67963\rev\9\Extern\G2MSetup8.12-8.20_IT.msi /qn /norestart /log output.log G2MRUNATLOGON=False','',*****,'15','_return',raUseSisAccount+WaitForExecution+raLogonWithProfile+raHideWindow+UndoneC... |
| 10:02:00.198 2 | clnexcln.dll: Security warning: UAC seems to be disabled for dsm_run. |
| 10:02:00.264 2 | xniTools: Created process with process id 2128 |
| 10:02:00.264 1 | xniTools: Waiting for process 15 minutes... |
| 10:17:00.278 2 | xniTools: Process execution timed out. |
| 10:17:00.279 1 | xniTools: Setting exit code variable '_return' to 'TimeOut' |
| 10:17:00.279 1 | Evaluating condition "not __return_='0'" | |
| 10:17:00.280 2 | Condition TRUE | -> entering IF part |
| 10:17:00.281 2 | -> ExitProcEx(Failed,'Installation mit Fehlercode TimeOut fehlgeschlagen') |
Hi bsteh,
Can you please check if you have User Settings configured which is capturing your Start Menu? This is in conflict with the way Ivanti Workspace Control tries to managed this. If you have that configured, disable (or remove) this User Setting and see if that solved the issue.
Regards,
Denise
Hallo,
ich kann dir leider nicht 100% sagen, wie es in der Version 8 aussieht. Aber ja, das Thema mit Gruppenrichtlinien in der Doku gibt es schon seit längerem. Ich hatte das damals so interpretiert, dass die Multi User Installation automatisch passiert, wenn die Installation im System Context läuft.
Dementsprechend sollte es theoretisch funktionieren, wenn du über den SIS Installierst, und DSM bei dir so konfiguriert ist, dass Local System herangezogen wird. Wenn das je nicht der Fall sein sollte (bei mir ists z.b. aktuell noch so), kann man sich auch mit PSEXEC behelfen.
Aktuell sieht der Aufruf (Execute) bei mir ca. so aus:
PsExec.exe -accepteula -i -s msiexec.exe /I C:\Verzeichniss...\G2MSetup7.30.6140_IT.msi G2MRUNATLOGON=false G2MPERFORMAVC=false G2MINTEGRATION=Outlook /qn
Gruß
Nico
GeoSync has no Hard limits in terms of Subscribers per Publisher, the main limitation will be hardware - CPU, Memory and I/O
Depending on how many users are at the remote sites, you may want to reduce the amount of daily syncs to some subscribers - this is possible but only via the PoSh cmdlets at present
Regards
Paul (EM - Product Manager)
Keep having to use the scrollbar as it is too stretched across the page.
This works on our other windows just not on the new window created? Any ideas? (Thank you)
We're currently deploying Ivanti Service Manager 2017.2 (On-Premise) and we're running into problems with the load-balanced aspects of the application. The License Server seems to be a single point of failure.
A high level overview of what we've configured is as follows:
UI servers (load-balanced with Azure Application Gateway):
Processing servers (load-balanced internally by Ivanti Service Manager):
The License Server on APP-01 has licenses installed for its MAC address and the target landscape has APP-01 registered. If the License Server service is stopped for any reason, the application fails gracefully.
If IIS is stopped on APP-01, an unhandled exception occurs:
{"Timestamp":new Date(1520855495619),"ErrorCode":"WebException","IsLogged":true,"IsUIReady":true,"InternalMessage":null,"LogEntryId":"c5bbd82a59fe4365a176856eccf74ef3","Message":"Unhandled system exception. See exception details in the application log.","StackTrace":null,"ExceptionType":null}
This message propagates to all application servers.
The current working theory is that the License Server is dependent on IIS, so when another application server attempts to access the system the following chain of events occurs:
If the License Server service is stopped but IIS is still available, the application gracefully handles the response from IIS and identifies there are no License Servers available. However, if IIS is unavailable there is no graceful response received and this presents itself as an Unhandled System Exception.
We want Ivanti Service Manager to still be available in the event of a failure on APP-01 so what is the correct way to achieve this? Can multiple License Servers be registered against a landscape? If so, will the application server access them round robin?
Kind Regards
Kevin Coady
Good afternoon
I'm looking into the Change workflow and am having some trouble identifying the Out of the box status's that come with the module.
There doesn't seem to be anywhere (I can find) where I can set the flow so the change automatically moves between the status's
I.E Draft - Requested - Pending Approval - Approved - Implemented - Closed.
In other Service Management tools I have used this status bar has been at the top of the Change request so you can see the progress, however in HEAT this is not the case.
Can anyone please advise where this are in the Admin console and how do I edit them/build them?
Many thanks
Dan
Try this route... Expose the field you want to drag in as an additional field, this may work out better for what you are doing.
Preview and submission work.
that worked!
Hi there ,
I'm new here and i hope to have an answer
we are installed recently the ivanti landesk , it's my first time with this tool
so , when i try to push the security patch and compliance to the endpoints machines some of theme get failed .
below the log file of a machine that cant get patched :
--------------------------
http://s0ldk01/Repository/fr_windows_10_Professional_version_1709_x64.iso
Échec
Échec : Impossible de télécharger http://s0ldk01/Repository/fr_windows_10_Professional_version_1709_x64.iso
Report des actions jusqu'à la prochaine fenêtre de maintenance.
Terminé
---------------------
Thank you for your help
The ones I have worked on typically have a command line argument to provide the password. Does this package have something similar?
That's great - thanks so much! It does just what I need
Thank you for the help. I'm installing a second server to hold both dev and uat; I'll install the ops console there. Your explanation has been helpful.
mmmm I have no idea...I'm looking into it at the moment. It's a Palo Alto product called Traps.
Hello there,
We have a few hundred machines that are under lease that are scheduled for return. I have a CSV with the Service Tags of the devices.
I am wondering if there is anyway to query our inventory based on service tags in the list and return the Computer Name, Service Tag, and the Model. I suppose I could do a SQL query directly on the database, but I was wondering if I can do that within the Console.
Thanks!
Thank you, The first scenario is what I am looking for, but I would like only the Workstation CI to populate, If I use only the second "dummy link" I get not return. If I combine the 2 I get all the CI's related to the customer.
I have errors that say compliance settings are not found on the Core, and have seen the KB doc that describes how to edit the Compliance settings, but in our installation (IEM 2017.3.2) the Agent Settings workspace does not contain anything about Compliance settings. How can I add that in?