I have created a PowerShell package to install an Outlook Plug-in. The script runs and is reported as a success but installing the .VSTO package does not occur. We install a certificate and download all the required files to the local PC but the plugin is not installed. If I run the PS script directly on the PC the entire operation runs and the plugin is installed. Is there something I need to do to allow the .VSTO file to run?
powershell scripts runs but does not install .vsto package
Auto Close after X -days
I have configured auto close same as this artical :
https://community.ivanti.com/docs/DOC-49380
But with no luck , it appears not effected when status is resolved
any thoughts why its not applied , or is tier some configuration should be checked in other places ?
Crystal Report Error
Hello
i followed this article for print button :
https://community.ivanti.com/docs/DOC-29998#comment-33676
when i'm trying to click on the "printer Icon" - it gives me an error , like attached
Thanks
View Reports button
upgrade using existing licenses
The upgrade guide menition that a new kind of licenses was introduced with RES ONE Workspace 2016.
We're planning to upgrade an existing installation (RES ONE Workspace 2015 SR2, version 9.10.2.0 SR2 Silver) directly to the latest version 10.3.
Are the already activated licenses automatically used and valid after the upgrade?
Or do we have to install licenses again?
Is there any way for the system to block user from receiving any notification from Ivanti Service Desk
Hi All,
I am wondering,
Is it possible for the system to block user from receiving notification either system wise or through database? Even though, the user have already been set into the required groups and roles and the members of the groups or roles are receiving notification from the system
If the answer is yes, where can I set or unset for the function mentioned above?
All of your answers will be greatly appreciated.
Thank you,
Best Regards,
Faiz
Dashboards really slow in Xtraction 2018-4
Dear Experts,
We have an instance of Xtraction 2018.4 which is recentlty installed and old instance 15.1.
We are building dashboards from the data from BMC remedy and I have joins between Incident and Survey forms in the datamodel.
When i pull out a score card component for example, old one takes fraction of second to provide me results. But the new one takes forever.
Is there anything i have to modify to opimize the performance.
Please assist.
Vinayak
AutoCad 2019 Package Deployment - 16439 (package installation timeout period has expired)
I've created a distribution package for AutoCAD 2019 that successfully installs on a target computer, however, on Management Console the task always displays an error 16439 (package installation timeout period has expired). I've tried extending the package timeout period from 2 hours to 4 hours but it didn't result in a different outcome.
Package Properties
Architecture Options: System Architecture
Install Options: /W /q /I \\landeskms\packages\AutoDesk\2019\Civil3Dx64\Img\Civil3Dx64.ini /language en-us
Additional Files: None (run from source)
Timeout settings: Enable package installation timeout (true), 4 Hours
Scheduled Task Properties
Task Settings: Policy-Supported Push, Accelerated push, Run from source (execute on share)
Running Management Console 2016.3
Any suggestions here?
new core transition
We decided to build a fresh server for 2018.3.
With that, I had heard/seen a presentation at a recent roundup that went something along the lines of getting the new core completely built up and tested and all that, and then when ready change the DNS entry of the old core to the IP of the new core and the devices should start showing up in the new core console where you can then start deploying the new agent, etc.
Is this the case? I changed the hosts file on a test device running 2017.3 and ran inventory scan and security scan. I haven't seen the device show up in my new core, so I wanted to make sure this was even a real process.
Thanks!
DELL WYSE THIN AGENT
Hello ,
I need to deploy the agent on dell wyse thin and embedded, on the agent configuration I only find the HP thin agent configuration.
I tested with the linux agent configuration on a dell wyse thin machine but the task still remains active without change!
We use a landesk 2017 Version 10.1.30.401
Any help please !!
ISM 2017.3 - Cannot display Custom Service Request Detail tab/form in MyItems for Mobile Self Service Role
Hi,
We are trying to expose a Service Request Panel/Form (Not the OOTB one but one we created instead) in the Mobile Self Service Role Like one is able to do with Inc and other Objects. We have managed to get it to work for the "Self Service Role" but it does not seem to work for "Mobile Self Service Role". Does anyone know if this is possible?
It might help to also explain how the requests are being Created: Because we have a few forms being shared by a few Hundred Request & Incidents we chose to use Form Offerings.
As a result we setup a custom object in order to setup the forms which we use to build the Form Offering. Once submitted the related Template creates the Incident or Service Request Record in the back-end. As a result there is no information on the Service Request Parameters.
The next step is then to Expose the Service Request Detail (The one we created) screen in the My Items Work-space on the Self Service Portal. Unfortunately this is where we find the challenge.
I followed the Steps listed below in order to configure the Service Request My Items form.
- I set a Custom Form in the Service Request Object
- In Roles & Permissions I selected Top Level Tabs
- I selected Mobile Self Service Role
- In object Service Request
- I select Business Object Form
- I then selected the form that I Setup
The result:
No Service Request Details which i setup (only the OOTB one which is blank but that is because the SR has not Parameters form, so expected)
I also cant seem to hide the detail, Cost and Delivery Info is also displayed - which i expected will not be
I then followed the Same steps for the Self Service Role:
The result:
The OOTB Detail Screen Black as expected
But the Form i setup Displayed Correctly
Has anyone been able to set this up successfully? or does anyone know if this is possible?
Task Query for Bulk Action
Hi,
I would like to write task query for Bulk Action. Basically, that query should be able to complete all the open tasks from the incidents.
Any help is appreciated.
Thanks,
Deepali
Calculation issue when creating a dynamic window
Morning everyone,
I am trying to create just the one Calculation so that when a user is selecting an option from the dropdown that it displays just the specific fields required.
I have the following, and the system doesn't seem to have an issue with it as the Test Syntax says that it's valid, however nothing changes no matter what you select from the drop down.
I was originally going to achieve this by using multiple individual calculations and they were working pretty much how I wanted, but thought that this would be a cleaner design.
My Dependancy is set to: _TransferType
import System
static def GetAttributeValue(Request):
if Request._TransferType != null and Request._TransferType._ReasonForTransfer == 'Contract Extension':
HideNewContractExpiryDate = false
MNewContractExpiryDate = true
HideOtherTempAccountChanges = true
MOtherTempAccountChanges = false
HideTemporaryPromotionEndDate = true
HideSecondmentReturn = true
HideUsersNewTitle = true
HideNewDept = true
HideNewLineManager = true
HideWillMoverBecomeLM = true
HideNewReporteesToBeInherited = true
HideNewMailboxAccess = true
HideNewSharepointAccess = true
HideMailboxRemoval = true
HideSharepointRemoval = true
HideNewSWForNewRoleRequired = true
HideNewSWSPNumber = true
HideCostCode = true
HideSoftwareAvailable = true
HideOtherEquipment = true
HideNewHWForTransfer = true
HideNewHWDetails = true
HideRingGroup = true
HideSurfaceProNumber = true
HideVCCUser = true
HideUsercurrentLM = true
HideNewSWForNewRoleRequired = true
HideSoftwaretoberemoved = true
HideWillMoverBecomeLM = true
HideNewSWForNewRole = true
HideSurfaceProAccessories = true
MSurfaceProAccessories = false
MSecondmentReturn = false
MVCCUser = false
MUsercurrentLM = false
MSurfaceProNumber = false
HideSurfaceProPen = true
MSurfaceProPen = false
HideLineManager = true
HideSecondmentRetunDate = true
MSecondmentRetunDate = false
HideSecondmentLocation = true
MSecondmentLocation = false
HidePrevunderlings = true
MPrevunderlings = false
HideLMToTakeOverReportees = true
HideOfficeMoveFrom = true
MOfficeMoveFrom = false
HideOfficeMoveTo = true
MOfficeMoveTo = false
if Request._TransferType != null and Request._TransferType._ReasonForTransfer == 'Career Break':
HideNewContractExpiryDate = false
MNewContractExpiryDate = true
HideOtherTempAccountChanges = true
MOtherTempAccountChanges = false
HideTemporaryPromotionEndDate = true
HideSecondmentReturn = true
All continue in the same way just with obviously a different Reason for Transfer and values.
There are 9 options from the dropdown, with each obviously showing different fields.
return String.Format(":SetHidden(_NewContractExpiryDate, {0});:SetMandatory(_NewContractExpiryDate, {1});:SetHidden(_OtherTempAccountChanges, {2});:SetMandatory(_OtherTempAccountChanges, {3});:SetHidden(_TemporaryPromotionEndDate, {4});:SetHidden(_SecondmentReturn, {5});:SetHidden(_UsersNewTitle, {6});:SetHidden(_NewDept, {7});:SetHidden(_NewLineManager, {8});:SetHidden(_WillMoverBecomeLM, {9});:SetHidden(_NewReporteesToBeInherited, {10});:SetHidden(_NewMailboxAccess, {11});:SetHidden(_NewSharepointAccess, {12});:SetHidden(_MailboxRemoval, {13});:SetHidden(_SharepointRemoval, {14});:SetHidden(_NewSWForNewRoleRequired, {15});:SetHidden(_NewSWSPNumber, {16});:SetHidden(_CostCode, {17});:SetHidden(_SoftwareAvailable, {18});:SetHidden(_OtherEquipment, {19});:SetHidden(_NewHWForTransfer, {20});:SetHidden(_NewHWDetails, {21});:SetHidden(_RingGroup, {22});:SetHidden(_SurfaceProNumber, {23});:SetHidden(_VCCUser, {24});:SetHidden(_UsercurrentLM, {25});:SetHidden(_NewSWForNewRoleRequired, {26});:SetHidden(_Softwaretoberemoved, {27});:SetHidden(_WillMoverBecomeLM, {28});:SetHidden(_NewSWForNewRole, {29});:SetHidden(_SurfaceProAccessories, {30});:SetMandatory(_SurfaceProAccessories, {31});:SetMandatory(_SecondmentReturn, {32};:SetMandatory(_VCCUser, {33});:SetMandatory(_UsercurrentLM, {34});:SetMandatory(_SurfaceProNumber, {35});:SetHidden(_SurfaceProPen, {36});:SetMandatory(_SurfaceProPen, {37});:SetHidden(_LineManager, {38});:SetHidden(_SecondmentRetunDate, {39});:SetMandatory(_SecondmentRetunDate, {40});:SetHidden(_SecondmentLocation, {41});:SetMandatory(_SecondmentLocation, {42});:SetHidden(_Prevunderlings, {43});:SetMandatory(_Prevunderlings, {44});:SetHidden(_LMToTakeOverReportees, {45});:SetHidden(_OfficeMoveFrom, {46});:SetMandatory(_OfficeMoveFrom, {47});:SetHidden(_OfficeMoveTo, {48});:SetMandatory(_OfficeMoveTo, {49});",HideNewContractExpiryDate,MNewContractExpiryDate,HideOtherTempAccountChanges,MOtherTempAccountChanges,HideTemporaryPromotionEndDate,HideSecondmentReturn,HideUsersNewTitle,HideNewDept,HideNewLineManager,HideWillMoverBecomeLM,HideNewReporteesToBeInherited,HideNewMailboxAccess,HideNewSharepointAccess,HideMailboxRemoval,HideSharepointRemoval,HideNewSWForNewRoleRequired,HideNewSWSPNumber,HideCostCode,HideSoftwareAvailable,HideOtherEquipment,HideNewHWForTransfer,HideNewHWDetails,HideRingGroup,HideSurfaceProNumber,HideVCCUser,HideUsercurrentLM,HideNewSWForNewRoleRequired,HideSoftwaretoberemoved,HideWillMoverBecomeLM,HideNewSWForNewRole,HideSurfaceProAccessories,MSurfaceProAccessories,MSecondmentReturn,MVCCUser,MUsercurrentLM,MSurfaceProNumber,HideSurfaceProPen,MSurfaceProPen,HideLineManager,HideSecondmentRetunDate,MSecondmentRetunDate,HideSecondmentLocation,MSecondmentLocation,HidePrevunderlings,MPrevunderlings,HideLMToTakeOverReportees,HideOfficeMoveFrom,MOfficeMoveFrom,HideOfficeMoveTo,MOfficeMoveTo)
I've got the Calculation showing on the screen, however the calculation box is empty, no matter whether it's empty or set to any of the 9 options.
I would really appreciate any advice, or whether there is a better way of achieving this?
Best regards,
Robin
Track number of survey request sent to customers in Service Manager.
I would like to be able to track the number of survey request send to customer along with the numbers of survey result received. Is this possible with a saved search or report.
Assigning incidents to a team in Service Manager
My company is transitioning from Service Desk to Service Manager. Our current assignment process allows us to assign to the entire support group or to analyst. The support group field is mandatory but the analyst field is not. I would like to setup the same process in Service Manager. I have created a new status labeled Waiting for Owner Assignment. The status would only require a selection of a team and not an owner for the assignment process. The status I following the rule Required Rule for Incident.OwnerTeam (Default) and making the selection of team and owner fields required. I am needing to know if it would be best to created a new required rule for this status or add an exception to the current rule. As I am new to this application I am unsure which option would correct or how to make this change. Thank you for your help on this issue.
Determine number of survey request sent to customers in Service Manager.
I would like to acquire numbers for surveys send out to Customers to determine the amount of surveys sent out versus the amount of answered surveys returned. Can this done with a saved search or report.
Transfer Linux server to new core
I do not see the option of "Create self-contained client installation package" for my Linux agent on the new core. What is the best way to transfer the linux box to my new 2018 core?
DSM 2018.1 - internal Windows Server 2019 Support - wann?
Habe soeben die erste Installation der finalen Windows Server 2019 Version mit DSM vorgenommen.
In Ermangelung des entsprechenden Supports in DSM habe ich einfach unsere Server 2016 Pakete kopiert und im OS Package die Sourcen getauscht.
Jetzt wäre es halt klasse wenn DSM das OS erkennen würde und man auch Pakete flaggen und Abfragen damit machen könnte.
Wann ist denn damit zu rechnen? Ist ja so, daß Microsoft schon lange Beta's verteilt hat und man diese zur Entwicklung hätte nutzen können.
Gruß
Mike
File Director 2018.3
Gents,
I did try to have a look into Install and Configure Guide, but it is really confusing for me, any idea regarding the installation! as video