lathey.blogg.se

1. #ADVANCED INSTALLER DESKTOP SHORTCUT INSTALL#
2. #ADVANCED INSTALLER DESKTOP SHORTCUT UPDATE#
3. #ADVANCED INSTALLER DESKTOP SHORTCUT CODE#

I have resolved the issue with the global shortcuts by simply starting the project over as a new project. I used the 'New Shortcut Wizard' in 'Files and Folders' to create the shortcut which placed a copy in the 'Application Folder' and 'Desktop' folder.Īm I missing something obvious here? Placing an icon on each users desktop does allow them to start the program.

#ADVANCED INSTALLER DESKTOP SHORTCUT INSTALL#

I'm satisfied with the results with the single exception that in all cases when attempting to install 'Only For Me (name)' instead of 'Everybody (all users)' I get a desktop shortcut on all users desktops (User\Public\Public Desktop) even though I only get a shortcut in the 'Start Menu' for the user logged on during the installation and the program is correctly installed in that user's Users\Name\AppData\. I've tried a significant number of different configurations (Media\Execution level, Dialogs\InstallTypeDlg, ShortcutsDLg, etc, and InstallationType\Per-User etc). There is probably a right way to do it but I opted for just simple detection.I'm trying to build a simple installation package that will allow any user to install our application regardless of administrative rights with the expectation that they will get the level of access appropriate for their rights and files will be installed in the appropriate folders (Program Files v.s. Otherwise, it might just try to revert the new auto updated app. & "C:\Program Files\Dell\CommandUpdate\dcu-cli.exe" /configure -lockSettings=enable - scheduleAction=DownloadInstallAndNotifyįor MSI deployments, make sure to tell it to not check versions. I think this PS command will work, just haven't had time to test it. I'm the only engineer working on setting up our Intune presence, so I'm spread a little thin. I'm working on a way to send a command line to tell it to auto update, but just haven't had time to get back to it.

#ADVANCED INSTALLER DESKTOP SHORTCUT UPDATE#

DCU will update itself when it runs updates on the computer. I now just deploy the Universal Dell Command Update as an App. I quit using the proactive remediation for Dell Command Update since that solution was, shall we say, unreliable.

#ADVANCED INSTALLER DESKTOP SHORTCUT CODE#

Your Detect code would need to check to see if the link was already there. $source.TargetPath = "C:\Program Files\Microsoft Office\root\Office16\WINWORD.EXE" $source = $new_object.CreateShortcut("$source_path") $source_path = Join-Path -Path $destination -ChildPath "Microsoft Word.lnk" $new_object = New-Object -ComObject WScript.Shell This the code that will put a Word shortcut onto the AllUsersDesktop (Public).

Here is the info on general Proactive Remediations: If not there, create one to avoid the issue. We suggest to feedback it to Intune user voicei in the following link (Intune user voice is a place where Product team collect some known issue, they will review it and may take it into consideration when deploying new version.)įor the second issue, based on my experience, we can modify the script to detect if the folder is there. Note: Non-Microsoft link, just for the reference.Īfterwards, I also test with other Win32 app and find the same issue. Here is a useful article about IME, we can read it as a reference:

Then I find the Win32 app is installed again. the installation is not started.Īs the information of Win32 app detected by IME agent is stored under HKLM\ SOFTWARE\Microsoft\EnterpriseDesktopAppManagement\\, I try to delete the registry key for this Win32 app, restart the client machine. Although the detection rule result shows false. Then I go to check the logs under "C:\ProgramData\ Microsoft\IntuneManagementExtension\Logs", I find that when the Intune Management Extension check the application status, the mode shows "DetectInstall". But a new Win32 app never deploy to the client. When I remove the desktop-shortcut manually, I find the record is also removed from "Device install status" of the win32 app. It must be absolute, so I can't even create the app.įor the issue you mentioned with self-healing, I have tested in my lab and find the same issue with you. I tried: install command: powershell.exe Copy-Item ".\shortcut.lnk" -Destination "C:\Users\$($env:USERNAME)\Desktop"īut, I cannot use "$($env" for detection rule path. Powershell.exe remove-item "c:\users\public\desktop\shortcut.lnk"Īssociated with a 32-bit app on 64-bit clients: Powershell.exe copy-item ".\shortcut.lnk" -destination "c:\users\public\desktop" I have used "Microsoft Win32 Content Prep Tool 1.8.1" to create a "*.intunewin" that contains the "shortcut.lnk", then created the app in Intune using the following to copy the shortcut to "C:\Users\Public\Desktop".