Shortcut Files in File Copy Operation…

[ajgreen]

Good Afternoon, I’m looking to copy a shortcut file as part of my Office 2019 deployment. Basically, I can’t find any other way to make the Skype for Business 2019 client startup for all users other than copying the shortcut file from “C:ProgramDataMicrosoftWindowsStart MenuPrograms” to the “C:ProgramDataMicrosoftWindowsStart MenuProgramsStartUp” folder. So I have the shortcut file on the local machine I’m running Batchpatch from, but when I go to select it in the Source file browser box, it says the file location isn’t available(which is understandable because Skype isn’t installed on the server I’m working off of). Any way around this? Or do I just need to install the Skype client on the server? Thank you for your help!

[doug]

I’m sorry to say that I don’t understand the problem that you’re describing.

If the file that you want to copy is placed on the BatchPatch computer in a folder like C:someFolderFileToCopy … and then you use the ‘copy files/folder’ feature and click the browse button for the source file/folder, you would then browse to C:someFolderFileToCopy to select the source file. I don’t understand what Skype not being installed has to do with it. You placed the file there manually, so the file is there regardless of whether or not Skype is installed. On the one hand you are saying that you select it in the source file browser box, but on the other hand you’re saying that you can’t select it in the source file browser box. So I’m confused as to what you are actually experiencing happen. Can you clarify?

[ajgreen]

Sure thing. I did some more testing, and I found out that it is when I click on any shortcut file in the browse window, windows attempts to go to that location. For instance, I have a shortcut to Batchpatch.exe on my local machine’s desktop, which points to the exe within a folder on the machine. In the source file/folder browse window, when I select that Batchpatch shortcut and press open, the location of my Batchpatch exe is placed in the source file/folder, and NOT the shortcut file itself.

My thought is that this is the way opening a shortcut is intended – to point the user directly to the location the shortcut is referencing. However, I don’t want to actually go to that location in this case, I want to select the shortcut file itself for copying.

So this really isn’t an issue with Batchpatch in any way. I’m working on a powershell script that will do what I need to do. I just need to copy the Skype for business shortcut located in C:ProgramDataMicrosoftWindowsStart MenuPrograms to the C:ProgramDataMicrosoftWindowsStart MenuProgramsStartUp folder. The first folder appears to be the default for all program launch icons for Office 2019(so in the start menu they aren’t under the Office folder anymore).

[doug]

Thanks for explaining. Yeah you are encountering a problem with how Windows Explorer is handling the ‘browse’. However, you can still do it with BatchPatch very simply. In that case you just can’t use the ‘browse’ button to specify the shortcut file. Instead just manually type or paste the filepath to the shortcut .lnk file. So for example:

Source file/folder (this computer) E:SomeFolderShortcut.lnk

Destination folder (target computer ): C:SomeFolder

[Author]

Posts