Every application is a puzzle for IT professionals to figure out when it comes to a customized, silent deployment. What switches will the setup accept? How can automatic updates be disabled? How can shortcuts be managed? How can system restarts be prevented?
March 16th, 2017
Productive virtual application debugging requires an understanding of the basic fundamentals of debugging compiled software code. For this part of my series on debugging virtual applications, I will be focusing exclusively on these fundamentals. If you are already familiar with these concepts, please allow me to quickly recap these to those readers which may be either not familiar, or only somewhat and looking to solidify these concepts.
February 24th, 2017
Recently I have been seeing many queries regarding shortcut icon not displayed after publishing a virtualized App-V 5.x package. The answer would be quite simple. But I would like to demonstrate it with a simple example so that it can shed some light.
February 17th, 2017
For many application packagers, virtual application sequencers, and general IT pros, the concept of actual “debugging” can take on many meanings. Often the words “troubleshooting” and “debugging” are interspersed – especially when reading articles and blogs dealing with the topic of trying to dissect what may be occurring when a virtual application is not functioning as expected. When we speak of the word “debugging” in the context of its meaning with regards to programming and compiled software code, it is simply the dissection and reverse engineering of binaries to determine the root cause of an issue or basically “find the bug” in the code.
February 9th, 2017
I guess every ConfigMgr Admin can confirm that getting the right LogFiles into CMTrace can sometimes be pretty challenging, due to the huge amount of actual LogFiles. I'm no difference here and in the past years, while troubleshooting ConfigMgr client side issues, I noticed that I always did the same repetitive tasks:
January 24th, 2017
Application Packagers usually spend some time in testing the virtualized applications in a standalone machine to confirm that the package is working fine and is issue free. In order to test the virtualized package using .appv, we need to open up a Powershell window as an administrator, and type in some Powershell commands. Though the commands are simple, they often require some time, which I feel can be reduced drastically. There are quite a few tools that provide options to test the packages without any need to do manual work, but not all customers want to use them in their environment. Hence, an idea to use a simple trick to install the App-V virtual packages in a single click without any need to open Powershell and type commands in a standalone machine. This can be achieved by a simple registry tweak to publish the virtual packages either globally, or to a user by right clicking an appv file, and using the context menu shortcut option.
January 18th, 2017
Upgraded every month by our team, since 2003.
You also might be interested in