A couple of weeks ago I created an AppV Tutorial for a customer. This tutorial is focused on the creation of a package with the AppV Sequencer 4.6, the import of a package in the AppV Management Console and the use of the package at the client side with the AppV Client.
Cheers!
When working with AppV I encountered a problem today when refreshing the AppV Client Management Console (sftcmc.msc). The virtual application was visible in the list of Applications but when launching it I received this error:
Error code: xxxxxx-xxxxxx39-0000010B
Solution:
Like mentioned in my previous post, I’m currently working with the SCSM 2010 in a lab environment. After reading a discussion on TechNet I wondered what the feeling must be to work in the Web Portal (Web Console) instead of the SCSM 2010 client. That’s why I installed the Web Portal on my virtual machine.
Before you can install the setup of the Web Portal you need an IIS Server to be configured. Because my VM is a DC, I installed the IIS (Web Server) Role on this machine.
Run the setup.exe (the same one you used to install the SCSM Management Server) and you’ll be presented with the “Microsoft System Center Service Manager Setup Wizard” where you have to choose to “Install the Service Manager Web Portals” .
“Getting started – Product Registration”: You can or fill in the Product Key or you can use the Trial Option (which will only last for 180 days). Read the EULA, mark it as read and click Next.
“Getting started – Installation Location”: Choose a location for the virtual website and be sure you have enough disk space to run it.
“Prerequisites – System Check Results”: The installation of the Web Portals will only proceed once all the prerequisites are fulfilled. The IIS 7.0 needs to be installed before you start the setup for the Web Portals (install the IIS role in the Server Manager).
“Configuration – Configure the Service Manager self-service portal name and port”: Choose a website name and port (the default port is 443 (HTTPS)) and select the server which will issue the SSL Certificate.
“Configuration – Select the Service Manager Database”: This is the page where the info is required of the Service Manager Management Server. As you can notice in the screenshot the SCSM database I use is the ServiceManager which is created on the SRV2008 SQL Server.
“Configuration – Configure The Account For The Service Manager Portals”: I kept the default setting (Local System Account).
“Configuration – Help Improve System Center Service Manager”: Off course I’m willing to participate in the Customer Experience Improvement Program!
“Configuration – Installation Summary”: You can check if all the settings and components you configured are correct. If so, press Install.
“Finished – Setup Completed Successfully”: As you can see in the text on the top of the page two portals were created. One for the end-user and one for the analyst.
On the bottom of the page you can see the additional option to open the “Encryption or Restore Wizard”. In this wizard you’re able to generate a key which can be used to encrypt or restore your settings.
More info:
Today I installed the SCSM 2010 in a lab environment and there where some issues I encountered during the installation. These issues will be explained during the series of screenshots.
“System Center Service Manager 2010 Setup” page installing the .NET Framework 3.5 SP1.
Once the .NET Framework was installed, the “Microsoft System Center Service Manager Setup Wizard” opened and I could choose between the “SM Management Server” and the “SM Data Warehouse Management Server”. I could notice a difference here for the requested memory. The “SM Management Server” needs 4 GB of RAM whereas the “SM Data Warehouse Management Server” needs 8 GB of RAM.
On the “Getting Started” page I did not register the software because I’m using it in a lab environment. If you are going to implement the software in your enterprise, be sure to request a license from Microsoft.
On the “Installation Location” page I didn’t change anything. Note that the System Center Service Manager only requires 1GB of free space!
The wizard is “Checking for requirements…”
On this page – “System Check Results” – I encountered some issues. First, my virtual machine did not have 4 GB of RAM allocated. I changed this and re-ran the installation. This issue was covered but the wizard showed me that the “Authorization Manager Hotfix” was not installed. I subscripted on the Microsoft webpage in order to receive the hotfix in my inbox. The email contained a link to the download location and a password for the .exe file. The .exe file will extract to a default location and the following file is generated: “Windows6.1-KB975332-x64.msu”. Run this file and the hotfix will be installed.
On the “Configure The Service Manager Database” page I lost some time because I did not install the SP1 for the SQL Server. Because of this the wizard could not locate the freshly installed SQL Server 2008. Once SP1 was installed, the wizard could locate the SQL Server and I decided to create a new database for the SCSM, called “ServiceManager”.
On the “Configure the Service Manager management group” I chose the name “ServiceManagers”. The persons in this group will be able to manage the SCSM 2010. The “sm\ServiceManagers” stands for the AD Group “ServiceManagers” in the domain “SM”.
“Configure The Account For Service Manager Services”
“Configure The Service Manager Workflow Account”
“Help Improve System Center Service Manager”
“Use Microsoft Update To Help Keep Your Computer Secure And Up-To-Date"
“Installation Summary”. Short overview of the completed wizard.
“Setup Completed Successfully”
“System Manager Management Console”. I’m now completely ready to go for it…
Documentation on Management Server
Documentation on Data Warehouse Management Server
Info on the installation of the Service Manager 2010 Beta 2 Data Warehouse Management Server
SCUG.be – System Center User Group
… and off course: Google
As my first contribution to the D-Spot I would like to give some more detailed information about a specific Microsoft Tool: ACT 5.5. This tool is mainly used to retrieve information from one or more computers. More info about the ACT can be found here.
The Microsoft Application Compatibility Toolkit (ACT) version 5.5 contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Windows 7, Windows Vista®, a Windows Update, or a new version of Windows® Internet Explorer® in your environment.
Before installing the ACT you need to have an SQL server installed. These are the SQL server versions you can use:
The client OS you can install the ACT on are all the client OS between Windows XP SP2 and Windows 7. The server OS needs to be at least Windows Server 2003 SP2.
When launching the installer of the ACT (Application Compatibility Toolkit.msi) a wizard starts and you need to go through the 6 steps. The wizard will ask you some questions about the SQL server database, log files, etc.
This is the main tool you use to manage the DCP’s (Data Collector Package) and all the retriever information from all the machines you ran the ACT on. The ACT is dependent from an agent (called a DCP) which you create in the ACM. In the following screenshots you can see how to create such a Data Collector Package.
Once you saved the msi-file you can start to distribute the package among all the computers you want the ACT to retrieve the information from. There are several ways to do this:
If the file has been run on a computer you’ll receive the information in the ACM. In the following set of screenshots the DCP will be run on a local machine and outputting the data to the same machine.
When the output is available in the ACM we can analyze all the information:
Be aware:
The “ACT Log Processing Service” needs to be started otherwise there will be no output shown in the ACM.
