Two Lesser Known Features of Login AM 2014 - Tracking Data Reset Dialog and Automatic Application Publication
Earlier this year we announced the general availability of Login AM 2014. In this blog I would like to share two features of Login AM 2014 with you that you might not be aware of, but can be very useful: tracking data reset dialog and automatic application publication.
Tracking Data Reset Dialog
Each time Automation Machine deploys a package to a system it creates a flag in the registry for that particular package. This flag in the registry helps Automation Machine to keep track of which packages have been installed in the past and prevents Automation Machine from deploying the same package twice. Especially when cloning computers or creating images based this tracking method comes in very handy since it makes the cloning/imaging process so much easier to handle. As an administrator you never really notice these flags since it is all handled internally.
Unless... you are the one that actually creates those Automation Machine packages. Automation requires testing. Depending on the level of complexity it may even require A LOT of testing. In these cases it doesn't help if you are constantly forced to connect to a remote machine to reset tracking data to redeploy a package. On top of that the registry key that stores the tracking data is filled with unreadable GUID's.
Please allow me to introduce our new tracking data reset dialog:
The tracking dialog allows you to remotely connect to a target computer and easily reset tracking data. Build, test and deploy FASTER :-).
Automatic Application Publication
Server Based Computing environments like Citrix XenApp or Microsoft RDSH often contain several if not hundreds of published applications. Managing these published application can take a lot of time.
In a DTAP scenarios where servers farms are fully seperated (as they should) maintaining a big list of published applications with all their settings can be a major cause of headache. If your farm has published applications that are not all consistently configured you might even run into some unexpected behavior that may cause your users to start multiple sessions on the same servers for no appearant reason.
With Login AM the administrator can enable automatic creation of published applications. So, in case of a farm (re-) build or an on-demand test environment build, all applications will automatically be published which saves a lot of time and prevents a lot of human errors.
I hope that these two lesser known features of Login AM 2014 will make your life a little bit easier. If you have any questions, please do not hesitate to contact us.