Thursday, March 24, 2011

SCCM client install failed with exit code 1603

You’ll notice this in your ccmsetup.log, MSI: Module C:\WINDOWS\system32\CCM\VAppRegHandler.dll failed to register.  HRESULT -2147221164. You need to register the atl.dll in order to make it works.

1. Perform ccmsetup /uninstall
2. Enter regsvr32 atl.dll in command prompt
3. Reinstall the client

Enjoy~! =)

Right Click Tools Install Client Failed with 0x80040281

The error code description is Failed in GetCertificate. This happens because the Right Click Tools is using an old ccmsetup.exe to install the client on your workstation and hence you failed with this error. To overcome this problem, you can copy the ccmsetup.exe in Program Files\Microsoft Configuration Manager\Client of your SCCM server and paste it to Windows\SCCMTools. Cheers, now you can install the client with the Right Click Tools again.

Monday, March 21, 2011

Remove App-V Servers From Management Console

According to this site, remove the App-V server from management console is easy as ABC. However this is not so straight forward, I faced a problem that the App Virt Management Console snap-in doesn’t exist in mmc.exe. To overcome this problem, you’ll need to modify the registry accordingly to this site. After the modification, the snap-in will appear in the mmc.exe and you can continue to delete your App-V server. Cheers~!!!

Monday, March 14, 2011

Toad 9 Sequencing Recipe

Before you begin with the sequencing, please make an appointment with the application team or person in charge of this application. You need to do it with them because they know the installation and configuration of their environment better than you.


1. Create a folder named Toad in Q drive of your sequencing virtual machine.
2. Launch the Virtualization Sequencer to create a new package.
3. Key-in the package name and begin monitoring on Q:\Toad
4. Begin the installation with Oracle client. Oracle 9i was used in this case.
5. Change the Oracle client installation path to Q:\Toad\oracle\ora92
6. After the installation completed, copy the .ORA files neccessary to Q:\Toad\oracle\ora92\network\ADMIN
7. After the configuration is done, begin the Toad installation.
8. Change the Toad installation destination path to Q:\Toad
9. Launch Toad in the physical environment after the installation completed
10. Enter the Authorazation Code and do the configuration needed
11. Check the TNS Database dropdown menu to confirm Toad is linking with the .ORA file
12. Do not try to login with any username. If you do that, the username will appear in virtual environment because it is still under monitoring step
13. Close Toad and stop monitoring
14. Choose the shortcut needed and remove those not required
15. Test launch Toad in virtual environment
16. Change the Protocol, Path, Hostname, and select the Operating System required
17. UNCHECK the Enforce Security Descriptor
18. Save the package to your content folder


Done... Now you're good in cooking Toad already. Happy cooking Chef~!!!

Friday, March 11, 2011

Solving Restriction Error To Folder In Virtual Environment a.k.a Bubble – Part 2

I’ve been doing research and looking from others solution on this error in my previous post for the pass few days. I found some similar error people faced out there provided with solutions and I decided to give it a try on my error. Without any luck, the solution doesn’t works for me. What I tried is I gave everyone full permission to the folder which I am sequencing. The purpose of doing this is to copy the permission into the virtual environment. But this is a good find out, you may want to give this a try and it might works on yours.

Wednesday, March 9, 2011

App-V: Branch Client Configuration for Streaming Server

Okay, talking about branch clients, of course you still can stream the virtualized applications directly from App-V Management Server. Many people misunderstand the functionality of the Management Server, the Management Server actually does application streaming as well. Therefore, you don’t need to setup a Streaming Server for the sack to stream the application. If you are worrying about the workload, then only you might want to try to setup a App-V streaming Server in your branch. The Streaming Server basically stream all the virtualized application to the client while the client is still manage by the Management Server.

I’ll not talk about the installation and configuration of the App-V Streaming Server. What I really want to share here is the configuration of the client in the branch. Like what I mentioned above, the clients will still manage by the Management Server but stream the application from the Streaming Server. There are registry that need to be changed in order to make this works.

1. Launch the registry editor and direct to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\Configuration
2. Double click the ApplicationSourceRoot located in the details pane
3. Enter the URL to your streaming server. For example, rtsp://streamingserver:554.
Noted: Replace the protocol if you are using others, replace streamingserver with your streaming server name, and replace 554 if you are using other port
4. Double click the AllowIndependentFileStreaming located in the details pane, and change the value to 1
5. Please delete all the virtual application in the client if it is previously streamed from Management Server
6. Refresh the publishing server
7. Go to the application tab and double click one of the application to view the properties of the application. Check whether the URL is changed to the application source root you entered in step 3. It should been changed if you follow the step properly.

That’s all, your App-V client is now streaming the application from the streaming server and yet manage by the management server. Other things that you may want to take note is the content folder of your streaming server. Please make sure that the content of Management Server and the content of Streaming Server are synchronized. There are few ways to do this, such as DFS, Robocopy or any other ways that you comfortable with.

Saturday, March 5, 2011

Solving Restriction Error To Folder In Virtual Environment a.k.a Bubble

Above is the error I have troubleshoot for few days. The application fail to launch because it require to write a file into the Q drive. This is not a problem for user inside App-V administrators group. Therefore the application must run as an user inside the administrator group for normal user. Below is the method that I tried but not successful.

I have tried to put in a vb script which will launch the application as an administrator during the sequencing. Unfortunately, the script is looking for the physical path instead of the virtual path. Here is the vb script I used:

Option explicit
Dim oShell
set oShell= Wscript.CreateObject("WScript.Shell")
'Replace the path with the program you wish to run c:\program files...
oShell.Run "RunAs /noprofile /user:testing\administrator ""Q:\Toad\TOAD.EXE"""
WScript.Sleep 100
'Replace the string --> yourpassword~ with the
'password used on your system. Include the tilde "~"
oShell.Sendkeys "P@ssw0rd~"
Wscript.Quit

After I realized that the script will look for the physical path, I got my second thought to modify the script to launch the application in physical path. Changed the 5th row to oShell.Run "RunAs /noprofile /user:testing\administrator ""C:\Program Files\Microsoft Application Virtualization Client\sfttray.exe /launch Toad for Oracle 9.0.1 9.0.1.8""". Still it is not working with an error saying that the App-V Client could not launch the application like the picture below.

Finally, I found the remedy. =) I disabled the security description during the sequencing like the picture below. If this setting is enabled, permission to the desired folder will copied to the bubble. Therefore causing the restriction error for normal user. For more information regarding this setting, you can refer to this.

Lastly, I still felt that the second method I used can be successful. I'm still working on it, stay tuned for futher updates. Have a nice day =)