Hi ,

I have a small doubt. Can you please advice if it is advisable for installing the application using run as option during the monitoring phase in app-v sequencing?

Kind Regards,
S.Yuvaraj.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Hi,

In order to clarify your doubt... before that i need to get clarified... why are you using Run as option when you are installing the application in monitoring phase.... whether it requires separate access like admin rights if so you can login in to that account and start installing the application.

when you are running runas option it will capture the user entries inside the monitoring phase, but however we are capturing everything in monitoring phase then it does'nt point out to any errors.

But reply back me like what exactly are you using this Runas option.

Regards,
Sunny
Answered 04/20/2010 by: sanath_sunny
Orange Belt

Please log in to comment
0
Hi ,

We are sequencing an application in server vm, where we are logging inot the machine using local administrator. But the application is installed by using the run as option since the application requires the domain id for installation.

Regards,
Yuvaraj.
Answered 04/23/2010 by: Yuvaraj_Subramanian
Senior Purple Belt

Please log in to comment
0
Application Virtualization
In Microsoft App-V programs are sequenced (prepared for virtualization) on a model system and then distributed. What you need to know about this style of application virtualization is that it will run for applications virtualized on Windows XP, Windows Vista, Windows Server 2003, Windows Server 2008, and it will work in future on Windows 7. These include the Terminal Server versions of the server OSs. Microsoft Application Virtualization distributes sequenced applications, either using an App-V infrastructure or Microsoft System Center Configuration Manager 2007 R2. For an application to be sequenced on one of the previously mentioned operating systems, it has to be able to run on it. If you have an application which will not run on Server 2003, Server 2003 Terminal Services, Server 2008, Server 2008 Terminal Services, Windows XP, Windows Vista, or Windows 7, App-V will not work for you. In this case, you would use Microsoft Enterprise Desktop Virtualization (MED-V). What MED-V does differently is that it combines computer virtualization with application virtualization for all of the benefits of application virtualization. For example, if your application only runs on Windows Server 2000, you cannot sequence that application to have it run with App-V. Windows 2000 can be virtualized itself with Virtual PC, Virtual Server, Hyper-V, or VMware, so MED-V sandboxes the Windows 2000 application in a virtual machine using a subset of Virtual PC and virtualizes the application in this way. Since Virtual PC is just an application or service running on top of an operating system, there is no problem launching the virtual instance of this application on a formerly incompatible operating system!
Answered 04/25/2010 by: plus2plus
Senior Yellow Belt

Please log in to comment
0
Yuvaraj,

Microsoft does have an official Windows 7 Support Forum located here http://social.technet.microsoft.com/Forums/en-US/category/w7itpro/ . It is supported by product specialists as well as engineers and support teams. You may want to also check the threads available there for additional assistance and guidance.

Jessica
Microsoft Windows Client Team
Answered 05/19/2010 by: JessicaD
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity