Ah - that'd explain why I've not seen this (suffering from a "duh" moment, as I only now noticed that you rightly put this in the "Macintosh" category...).
I'll try to get someone with some knowledge to look at this .
↧
Re: 3rd Party Preference Pane Issues
↧
Re: Linux Removal of Agent
It would help if you'd clarify what you mean (specifically) by "duplicate ID" ...?
If we're talking about "duplicate device ID" (as referenced in this article here -- About: "Devices" and "Duplicate ID's" option for Inventory, and how they work ), then be aware that the relevant tech doesn't work (yet) on NIX-devices, as rather than talking to the Inventory Service directly (and thus being able to be told "Hey, I already have a device ID for you - you should really restore your old one") isn't presently possible.
That would be an enhancement request, which you can file here -- Enhancement Requests --.
If you're talking about something else (as "duplicate ID") then please clarify what you're talking about, so we can talk the same language .
↧
↧
Re: Manual update of IM_Incident_Resolution (under SQL)
JohnO I presume the errors you mean are from trying to map these fields in a Data Import right. The 4 fields above are presumably on the Resolution object to.
I cant see any reason you cant import directing into this object from SQL and populate these fields too. Just remember to poke the parent Incident GUID in the related attribute to create the relationship.
Always try in DEV first though and with just one row you can test on.
Julian
MarXtar Ltd
↧
Re: Velocity WEB: Screen wakeup event / Keyboard always shown
Thomas,
every user wants something else - why there is no setting in WEB emulation as in Telnet to configure keyboard visibility "by design"?
↧
Fixing Intel NUCs so they can get Provisioned
Hi there everyone,
I'm not sure if I'm posting this in the correct location, but I spent a while working with the guys from LANDesk a while back in order to try and get an Intel NUC to build... it was refusing to build as it would Timeout looking for the Provisioning Template, and as I know I'm not the only one that will have this issue I figured I would put down what I did to resolve the problem, as it could save you a lot of time.
I tried a number of things such as trying to Provision of the OS from PXE boot, a bootable USB and even trying to Provision from an already running Intel NUC (with just the Agent installed).
After a while we changed some settings in LANDesk Management Console for it to look for MAC address instead of serial number, after that was changed the NUC built.
In our setup we don’t want to use MAC addresses to identify the device as we have a number of USB Ethernet Dongles which have the MAC addresses assigned to them, so moving them around machines can confuse LANDesk Management Console.
After finding out that MAC Address worked, I looked around in the BIOS and found that the Serial number, Manufacturer, Product Name and Version were all showing under “Board Information”, however both the Chassis and System Information sections in the BIOS were blank.
Based on that, I looked around online and I managed to find some information where someone had a similar issue with MDT and the NUCs, he explained how he used the "Intel Integrator Toolkit 6.1.8" tool to modify the BIOS in these sections.
I then downloaded the tool from: https://downloadcenter.intel.com/download/26307/Intel-Integrator-Toolkit, extracted the ITK6.UEFI file and saved saved it on to a FAT32 formatted USB.
I needed to get the serial number of the device and some other details, as well as change some BIOS settings,
On my Intel NUC that was achieved by doing the following:
I booted into BIOS (Pressing F2 on Bootup in my case)
I went to the screen that showed the serial number (Image above), and noted down the Manufacturer, Product Name, Version and Serial Number
Then you need to enable the Internal UEFI Shell in the BIOS
Click Advanced
Click on Boot at the top
In the Boot Screen click on the Boot Configuration
Under Boot Devices tick the Internal UEFI Shell box
Save the settings and exit.
Press F10 to Enter Boot Menu
Select UEFI : Built-in EFI Shell
Once your booted into the shell, it’s just a matter of typing a few commands to input the details you want to enter.
I’ve done it a few times now on different NUCS and the second and third time it’s a lot easier as I now know what I am doing, the first time was a little guesswork.
I skipped a number of the settings which I knew weren't needed for my case such as SKU and Asset Tag, but you may want to add these for your situation, you will just need to use SKU or Asset after the -f in the steps below
Below I will be using the following details for an example (changed the serial number), to give you a better idea how it looks
Serial : GERY123456789F8
Manufacturer : “Intel Corporation”
Version : H40999-504
Product : NUC5i5RYB
The commands to type once it's booted and you have changed to the correct drive (usually one of the following drives fs0:, fs1: or fs2:) are below
ITK6 -s -p (this will show you the fields that are empty, you can also run this at any stage to see if your changes have taken place).
ITK6 -s -t System -f Serial -v GERY123456789F8
ITK6 -s -t Chassis -f Serial -v GERY123456789F8
(Replace GERY123456789F8 with your devices serial number)
ITK6 -s -t System -f Manufacturer -v "Intel Corporation"
ITK6 -s -t Chassis -f Manufacturer -v "Intel Corporation"
ITK6 -s -t System -f Version -v H40999-504
ITK6 -s -t Chassis -f Version -v H40999-504
(Replace H40999-504 with your version number from BIOS)
ITK6 -s -t System -f Product -v NUC5i5RYB
(Replace NUC5iRYB with your devices Product name from BIOS)
Note that Product is only used for the System, and not for Chassis like the others do.
Confirm the details you have entered above have all gone in correctly by using the following command
ITK6 -s -p
You should see that the missing fields now have the information entered.
Reboot and confirm again in the BIOS settings.
If so then feel free to turn off the Internal UEFI Shell boot setting in the BIOS, then reboot and provision your machine.
Hopefully this helps those of you that like me have spent hours tearing your hair out it over a simple Provisioning Template timing out on the Intel NUCs.
While I've marked this down as 2016.x, it is likely it affects other versions of the Management Console as well.
↧
↧
Re: API - Does every API call require a PSCredential?
Micah,
Our API does not have a token service. It uses challenge response authentication via Kerberos/Negotiate/NTLM authentication. This is necessary because many of the non-agent and credential operations we support actually require a user profile or impersonation of specific user.
You should not need to configure delegation. The reason that the API accepts a ‘RUN AS’ credential is explicitly to prevent the need for delegation. In theory, you could configure delegation and use the Integrated Windows authorization token for a remote assessment/deploy operation. However, that is non-typical GPO/Local Security Policy setting and is not something we can require.
You should absolutely be able to use your local integrated Windows Identity if you can use it to log-in into the Console/Server GUI.
The requirements are:
- The user is part of the local administrators group on the ISeC Console/Server.
- You specify -UseDefaultCredentials on the Invoke-WebRequest PowerShell method.
- Alternatively, you could specify alternate credentials on Invoke-WebRequest via with a PSCredential object.
- Another way to test authentication is GET via the Postman App (Using NTLM and SSL validation disabled) or directly via a web browser:
- A simple GET API method should work. For example:
- https://{ISeCServerFqdn}:3121/st/console/api/v1.0/patch/patchmetadata
If you are still having issues, please post your sample PowerShell script or command. The team would be happy to assist.
Other things to consider:
- Are you subject to remote UAC restrictions?
- Do you have an additional Local Security Policy or GPO setting preventing NTLM authentication?
↧
Re: Request Offering Data Storage
Hi Jsnurr,
You can refer tables below:
ServiceReqParam - Value entered by user, 1 record per parameter value
ServiceReqTemplateParam - Request Offering's Parameter, 1 record per parameter
ServiceReqTemplate - Request Offering, 1 record per offering
↧
Re: Remove the "Data in the database has changed while you were editing" verbiage from validation rule pop-up
Thanks for the update.
↧
Updating Master-Incident through Incident
Hello everybody,
do any of you have experience with Master-Incidents and the possibility of updating its information through linked Incidents?
I know how to update fields of Incidents with Task.Assignments but the MI to I relation is less comprehensible.
Kind Regards
↧
↧
Festplatte annähernd voll, keine Pakete (somit auch keine Patches) werden mehr installiert
Hallo zusammen,
habe hier ein paar Rechner wo ich mich gewundert habe das neue Pakete und Patches nicht installiert werden.
Beim überprüfen habe ich festgestellt, das die Festplatte fast voll war.Da ja Plattenplatz für DSM wichtig ist, wäre es doch eigentlich gut, wenn der DSM Agent bei unterschreiten bestimmter Werte selbständig den User informiert, das nur noch wenig Plattenplatz vorhanden ist und man aufräumen sollte, weil sonst keine Software und keine Sicherheitsupdates installiert werden können.
Das Thema gab es hier bzw. bei Heat oder Frontrange, glaube ich, schonmal. Und ich bin mir nicht mehr sicher, ob es da hieß, das es solche Hinweise beim neuen DSM geben soll, gibt es das jetzt oder nicht?
Grüße,
Oliver
↧
Possibility of selecting the a HEAT Development Project from the Service Desk Console
Hi,
We have the possibility of selecting a development project in the back end as shown below:
I will like to know if someone has made it possible to select a project from the Service Desk Console. Basically having the same option above from the front end instead?
TIA.
↧
Re: Updating Master-Incident through Incident
Hi,
You might check this link on how to work with Master Incident in ISM: https://help.ivanti.com/ht/help/en_US/ISM/2017/Content/ServiceDesk/Incidents/Master%20Incidents.htm
If this link does not help, could you please specify exactly on how you want to update the linked Incidents?
↧
Windows 10 1809 RSAT Tools und Unterbindung der Verbindung zu Windows Updates...
Hallo zusammen,
mit Windows 10 1809 hat Microsoft die Installation/Aktivierung der RSAT Tools geändert.
Man installiert sie nicht mehr, sondern muss sie im Windows als zusätzliches Feature (einzeln) aktivieren.
Windows zieht sich die dann direkt von Microsoft.
Das kann man auch per Powershell machen. ( https://www.faq-o-matic.net/2018/11/21/rsat-fr-windows-10-v1809-total-easy/ )
Dafür muss aber der Zugriff auf Microsoft erlaubt sein (GPOs überprüfen).
Ich hatte Windows Updates und den Zugriff auf MS per GPOs konfiguriert und untersagt, damit ganz sicher alles über Patchlink bzw. APM gepatcht wird und auch Windows 10 nicht über den Ausweichweg sich Updates holt.
Jetzt musste ich für die RSAT Tools das ganze wieder etwas mehr aufmachen, mal sehen ob es nicht zuweit offen ist und sich Win10 selbst wieder Updats holt und nicht über APM geht.
Grüße,
Oliver
↧
↧
Re: Device Status not showing correctly
Hi,
I haven't got this issue resolved overall yet however I found that we had some issues with our setup of Windows 10 devices which I am currently resolving which will resolve this issue I hope. I have engaged our Network and Inf teams just to make sure there is nothing wrong that side of things. I did raise a support ticket however I decided to close it until I have fixed Windows 10 and confirmed with Network and INF that we have no issues network wise and DNS wise. If this is still an issue after all this I will raise a support ticket. I am hoping it's a network or DNS issue and I can get it fixed soon.
Kind regards,
Luke
↧
Could not make files available for job..... "Der Transport des Dateipakets wurde unterbrochen. (0xe0090012)
Hallo zusammen,
kennt das evtl. jemand, wenn ein Paket verteilt werden soll (in dem Dateien/Programme sind) dann scheitert das beim ersten Versuch mit "Could not make files available for job..... "Der Transport des Dateipakets wurde unterbrochen. (0xe0090012)" beim erneuten Anstoß, wird es ohne Probleme installiert?
Ich kämpfe noch damit, die Ursache heraus zu finden. Es könnte der SEP (Symantec) sein oder auch Windows. Aber in den "Standard" Logs finde ich nichts dazu. :-(
Grüße,
Oliver
↧
Re: Windows 10 1809 RSAT Tools und Unterbindung der Verbindung zu Windows Updates...
Hallo Oliver,
Danke für die Infos. Ob das per SCCM auch nur über diesen Umweg geht?
Oder kann man die ISO-Abbilder mit den enthaltenen FoD verwenden? Eigentlich müssen die ja dafür gemacht sein...
Ich will Windows 7 behalten...
Gruß
Nils
↧
Re: Windows 10 1809 RSAT Tools und Unterbindung der Verbindung zu Windows Updates...
Hi Nils,
soweit ich das in den letzten Tagen gelesen habe geht das nur manuell in Windows oder halt mit Powershell (damit klappt es echt gut). Was da auf dem DVDs ist, soll die RSAT Tools nicht enthalten.
Der Powershell Aufruf in dem verlinkten Artikel, installiert alle RSAT Tools, es gibt im Internet diverse Quellen, wo auch beschrieben ist, wie man per Powershell nur einzelne Tools aus dem RSAT installiert.
Grüße,
Oliver
↧
↧
Re: Windows 10 1809 RSAT Tools und Unterbindung der Verbindung zu Windows Updates...
Hallo Oliver,
schau mal hier.
Hiermit kann man wohl die Feautures on Demand aus dem ISO-Abbild einbinden. Der entscheidende Punkt ist wohl der PowerShell-Befehl:
Add-WindowsCapability-Name $FeaturesHash[$Feature] -Online -LimitAccess -Source $dir\sources
Das wird wohl helfen, damit man keine Internet-Verbindung braucht und per DSM die Tools verteilen kann.
Gruß
Nils
↧
Re: Boo query - condition - contains or starts with
Hello,
It don't work for me :
An Idea ?
↧
Landesk GETremoteLog MBSDK
Hi I'm trying to get event logs from a machine using mBSDK
I get success return code, however no data, Please assist, does the log gets stored somewhere?
↧