This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies.
For details on cookie usage on our site, read our Privacy Policy
For details on cookie usage on our site, read our Privacy Policy
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
About m455954
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- LIVEcommunity
- About m455954
12-21-2020
2Posts
1Like
0Solutions
Dec 21, 2020Last Visited
User
Activity
User
Profile
Latest posts by m455954
| Subject | Views | Posted |
|---|---|---|
| 4347 | 12-03-2020 04:40 PM | |
| 4387 | 12-03-2020 02:05 PM |
My Liked Posts
| Subject | Likes | Posted |
|---|---|---|
| 1 Like | 12-03-2020 02:05 PM |
User Badges
Community Statistics
| Member Since | 12-03-2020 01:54 PM |
| Date Last Visited | 12-21-2020 12:34 PM |
| Posts | 2 |
| Total Likes Received | 1 |
12-03-2020
04:40 PM
Thanks for the reply, but I don't have a problem with the client not installing correctly if I run it manually, it's more about how I can deploy it. The deployment within InTune allows me to deploy a single .pkg file, and if I deploy the standard Cortex XDR.pkg file in that way it installs fine, but can't connect as it has no config. I can't deploy the Config.xml file alongside the .pkg file when done like that. So I tried to package up the Cortex XDR.pkg and the corresponding Config.xml into another package using the Packager app, and have a postinstall.sh file which runs the installer command line to kick off the installation of the Cortex XDR.pkg file now that it will have the Config.xml file with it - but that's not working at present - and I'm not sure why. What I was aksing was if there's a way to embed the config info into the pkg file directly rather than needing to have the Config.xml file, as then I could use the single .pkg file and it should just work. The documentation for deploying the Mac client shows either the manual installation, of for the Jamf deployment shows how to set up the extension policy, but nothing else - so I'm a bit in the dark about if I'm even trying to do this right. I've learnt more than I ever wanted to know about Mac packaging in the last week and am really none the wiser 🙂 Hoping someone else on here has already been through this pain and has a simple method to get it working. Cheers, Mark.
... View more
12-03-2020
02:05 PM
1 Kudo
Hi all, We're trying to bring our few Macs into the systems management fold, and being a Microsoft shop we want to use InTune to manage them. Most Mac packages install files and then are configured in a separate set of commands after install. The XDR Mac client needs the config.xml file in place beside the Cortex XDR.pkg file when installing. I've tried creating a package (using the 'Packages' app) with the xml and pkg files in it and then running a postinstall script as part of that package to kick off the Cortext install using 'installer' as a bash command - but although the files get deployed the Coretex client never gets installed. Am I going about this the wrong way? Is there a way of modifying the Coretex XDR.pkg file to embed the Config.xml bits inside it so I can just deploy that package directly? Has anyone successfully deployed this client using InTune? Any help would be gratefully received. Mark.
... View more
LEGAL NOTICES
Copyright 2007 - 2022 - Palo Alto Networks