(This condition will only appear on the Install and PowerShell steps) Select the version or versions of PowerShell for which the package will be applied. Tearing my hair out on getting the shortcut to arrive on target device with the correct favicon displayed.Select the version or versions of Windows for which the package will be applied.Ĭhoose whether the package is to run on 32-bit, 64-bit, or both operating system architectures. I'm aware PS scripts could do this but PS scripts (and vbs scripts) are restricted in my environment and PDQ won't let me, or at least I don't know how to, get my commands to run from an elevated prompt through a package. They all work fine for creating the shortcut, but the moment I push the shortcut to the target device it loses the icon it's supposed to have. I've searched everywhere and tried numerous ways to make the shortcut file: drag n drop, settings>more tools>create shortcut, using notepad to make. But recently when I try deploying that particular package the shortcuts show up on the desktop with blank page icons. It would show up on the target device, would open with the default browser, and most importantly it properly displayed the favicon. ![]() It used to work just fine having created the shortcuts with the drag and drop method from the url address bar, placing that shortcut into my PDQ repository folder, and then user PDQ to push the shortcut. I am trying to use PDQ deploy to push desktop shortcuts to devices.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |