Howto deploy a Federated Search Connector in Windows 7

Howto deploy a Federated Search Connector in Windows 7

Yesterday we had a kickoff for an Early Adopter Windows 7 Community @ Microsoft in the Netherlands.
One of the presentations was about Federated Search and how this nice option will make our work much easier.

Some people were wondering howto deploy a Federated Search Connector in an Enterprise Environment, but nobody seems to know the answer. Reason for me to find out how to do this.

As for most solutions, it is not the only or the best solution, but because I like Group Policy Preferences (GPP) so much I developed a way to deploy a search connector using GPP.

In this example I will deploy the Youtube connector.
(Look for more connectors on : http://www.sevenforums.com/tutorials/742-windows-7-search-federation-providers.html)

On an admin PC just doubleclick on the downloade file, this will install the Search Connector on your PC, in fact it will install it in your user profile.

Now we need 2 files from your profile, first look up C:\USERS\<YOUR USERNAME>\LINKS\YOUTUBE.LNK
Before you copy this file right click it, choose properties and change the targetlocation to : C:\Users\%USERNAME%\Searches\Youtube.searchConnector-ms

Now copy this file to for example your NETLOGON share.

After that copy the file C:\USERS\<YOUR USERNAME>\SEARCHES\Youtube.searchConnector-ms to the NETLOGON share.

We’ve got the files that we need to deploy it to our users.

Logon to your domain controller (or the machine that you use to manage Group Policy) and open the Group Policy Management Console.
N.B. To manage Group Policy Preferences you need a Windows Server 2008 (R2), Windows Vista or Windows 7 machine.

Open your User policy and expand the User Configuration node.
Now go to Preferences -> Windows Settings -> Files.

Add these 2 files :

 

If you close the file screens, the preference screen will look like this (except for my domain name ;)

Now the only thing you have to do is wait until the user policy is refreshed ( a user does not have to take any action and will see the search provider automaticly)
And if you cant wait, just use the good old GPUPDATE.

Thats it for now, please enjoy.

Regards,

Erik

Read More

If Windows Vista Update fails with error 80245003

Maby you have this problem: You try to update your Windows Vista RC1 / RC2 desktop and you get the error that you cannot update with error 80245003

Then you can try this what i found on the net:

Rename the SoftwareDistribution folder (it will be recreated next time you visit
WU again)
You will lose your history but that’s not important.
Click Start, Choose Run.
In the Run box, type services.msc.
Click OK.
Right-click the Automatic Updates service.
Click Stop.
Stopping the service will take a moment.
Rename the “SoftwareDistribution” folder:
a. Click Start, click Run, type %systemroot%, and then click OK.
b. Right-click the SoftwareDistribution folder, and then click Rename.
c. Type SoftwareDistribution.old, and then press ENTER to rename this folder.

Click Start. Choose Run.
In the Run box, type services.msc.
Click OK.
Right-click the Automatic Updates service.
Click Start.
Starting the service will take a moment.

This worked for me.

This worked for me.see ya

Jeroen Jansen

Read More

Running MS Virtual PC 2004 smoothly on Vista

Though it’s easy to install VPC2004 on the Vista beta builds, getting it to run smoothly is another story. This is how I got mine working with acceptable performance and behaviour

1. – Use the latest Vista beta (build 5456). This build is noticeably faster than 5384, but at the cost of some stability. If you’re using a Dell Latitude D810, don’t install the Dell modem and WLAN drivers with this build because they will break things or make your system BSOD. Also, don’t enable your WLAN/Bluetooth radios while Vista is running, your system will BSOD also. The things you have to put up with for a fast build….

2. – Install Virtual PC 2004 with SP1. This is important, don’t install Virtual PC 2004 RTM and then  upgrade to SP1; use the SP1-integrated version.

3. – Install Virtual Server 2005 R2 Enterprise. Only install the Virtual Server services; don’t install the documentation, VMRC or Web Console. You now get the latest VMM.SYS and the Virtual Machine Additions that work with Windows 2003 SP1. If you want to run Vista on your Virtual Machine, you should download the “Virtual Machine Additions for Beta 2″ from the Microsoft Connect site. You can find this in the “Virtual Server 2005 R2 SP1 beta” program.

4. – Change the Startup Type of the “Virtual Server” service from Automatic to Manual and stop the service if it is running.

5. – Download the Virtual PC hotfixes zipfile here and extract the following file: vpc2004qfe899525_msdn.msp.

6. – Ensure that you don’t have any virtual machines running and that you do not have the Virtual Machine console started. Run the vpc2004qfe899525_msdn.msp update.

7. – Apply the following instructions from the KB899525 hotfix article:
I. Navigate to %root%\Users\%username%\AppData\Roaming\Microsoft\Virtual PC.
II. Right-click the Options.xml file, and then click Edit.
III. Add the following code to the file.

<virtual_machines>
<enable_idle_thread type=”boolean”>true</enable_idle_thread>
</virtual_machines>

Now your virtual machines should run smoothly!

Read More

Automate 3rd party software, drivers and BIOS updates with the new System Center Update Publisher 2011

With System Center Update Publisher (SCUP) Microsoft provides a platform for adding 3rdparty updates to your conventional WSUS updates. Until last week SCUP 4.5 was available for adding 3rd party software, driver and BIOS updates to a WSUS server. With SCUP you can either use a catalog file to import multiple updates from a vendor’s website at once or just simply add your own update packages to SCUP to deploy it in your enterprise environment as they were Microsoft updates. Now, with SCUP 4.5 there were some issues which are resolved within SCUP 2011. Some of the issues include the following:

  • Limited configuration options for download behavior (i.e. metadata only vs full content)
  • Expired updates cannot be removed from the updates server easily
  • Approval and publishing updates requires multiple steps to be taken

With SCUP 2011 you now have a so called ConfigMgr integration. This integration option can be used to regulate download behavior for an update. In general you probably want clients to download only metadata from SCCM/SCUP if only a few clients request an update. When the number of clients increase it would be better to download full content so that clients will use common distribution points instead of an internet location to download the update to avoid unnecessary bandwidth utilization. With the thresholds you can regulate this now.

Expiring and removing updates properly was a hell of a job if an update was removed from a vendor’s catalog. In SCUP 2011 you can use a new Software Update Cleanup Wizard for this. So now, expiring a software update that exists on the update server but is not in the SCUP repository is an easy job.

SCUP 2011 has a Publish tab where you can bundle updates that you want to deploy to your clients. This is a new feature that makes it somewhat easier to manage and administer the SCUP update repository.

What I like the most about SCUP is that you are able to deploy software with the WSUS functionality available. In large enterprise environments normal software distribution requires lots of steps to be taken by various departments for each individual software update. These steps include scripting, testing, configure SCCM packages, collections, advertisements, etc. New software updates like Adobe’s Flash Player are being released very rapidly. It requires that you’ll have to execute the same procedure over again to deploy it in your enterprise. Using SCUP and Adobe’s update catalog instead will save you a lot of time.

Installing drivers, BIOS, hardware utilities and firmware for instance on Dell systems is an easy job using SCUP. Minor disadvantage is that you will need the OpenManage client running on client systems to provide some necessary WMI classes. These extra classes will be used to identify the hardware peripherals. WSUS uses this information to compare with the catalog logic rules:

s002

 

With SCUP you can use the logic which comes with the catalogs to deploy a software update bundle that include multiple updates at once. Compare the logic within the catalog with the queries you normally use in SCCM collections for grouping the client systems what you’ll need for targeting the software.

You can also create your own updates. As an example i’ve added the Google Chrome browser installer as a required update with Adobe Flash Player as a prerequisite :-)

s003

Read More

HOWTO: Bitlocker Status Reporting in SCCM 2007

I recently had to come up with a solution that will enable administrators to build reports for client’s bitlocker status. To do so i found a few articles on the web that pointed me in the right direction, however i didn’t found a complete howto for it so that’s a good reason for me to post a complete one.

To enable bitlocker status reporting in a centralised management environment with SCCM you need to follow some steps because bitlocker is not integrated that far (yet??) in the Windows OS. First, let’s first take a look at the status information that bitlocker provides:

  • Volume name, example: C: [OSDisk]
  • Disk size, example: 148,75 GB
  • BitLocker Version, example: Windows 7
  • Conversion Status, example: Fully Encrypted
  • Percentage Encrypted, example: 100%
  • Encryption Method, example: AES 128 with Diffuser
  • Protection Status, example: Protection On
  • Lock Status, example: Unlocked
  • Identification Field, example: None
  • Key Protectors (Note: multivalue), example: TPM, Numerical Password

You can check the above on clients using the commandline tool manage-bde.exe -status on Windows 7 clients. For Vista clients use cscript manage-bde.wsf -status.

Step 1. Modify and deploy SMS_DEF.MOF

We want bitlocker status information to be inventoried to SCCM. A proper way of doing that would be to add the bitlocker class to the SMS_DEF.MOF file on the management point (found in %SCCMinstallpath%\inboxes\clifiles.src\hinv). Make a copy of this file and edit with your favorite app. Add the following lines at the end of the file:

#pragma namespace (“\\\\.\\root\\cimv2\\SMS”) //make sure to use normal quotes!
#pragma deleteclass(“SCCM_BitLocker”,NOFAIL)
[ SMS_Report     (TRUE),
SMS_Group_Name (“SCCM_BitLocker”),
SMS_Class_ID   (“CUSTOM|SCCM_BitLocker|1.0″) ]
class SCCM_BitLocker : SMS_Class_Template
{
[SMS_Report (TRUE), key ] string Drive;
[SMS_Report (TRUE)] string DriveLabel;
[SMS_Report (TRUE)] string Size;
[SMS_Report (TRUE)] string BitLocker_Version;
[SMS_Report (TRUE)] string Conversion_Status;
[SMS_Report (TRUE)] string Percentage_Encrypted;
[SMS_Report (TRUE)] string Encryption_Method;
[SMS_Report (TRUE)] string Protection_Status;
[SMS_Report (TRUE)] string Lock_Status;
[SMS_Report (TRUE)] string Identification_Field;
[SMS_Report (TRUE)] string Key_Protectors;
[SMS_Report (TRUE)] string Automatic_Unlock;
[SMS_Report (TRUE)] string ScriptLastRun;
};

[edit] Make sure to replace any fancy double quotes with normal quotes after copying because otherwise compiling or parsing will fail. Or download this file: bitlocker_mof.

You should check the file for errors with mofcomp.exe -check SMS_DEF.MOF. To enable the MOF file on a single client run the following command on the client mofcomp -class:forceupdate %pathtofile%\SMS_DEF.MOF. Copy the edited file back to enable it on your ConfigMgr site.

Step 2. Install Bitlocker

Create and link a GPO to apply on the bitlocker clients that contain the following settings (or similair based on your own requirements):

Machine | Administrative Templates | System | Trusted Platform Module Services
Turn on TPM backup to Active Directory Domain Services Enabled
Machine | Administrative Templates | Windows Components | BitLocker Drive Encryption | Operating Sytem Drives
Choose how BitLocker-protected operating system drives can be recovered Enabled
Allow data recovery agent Disabled
Configure user storage of BitLocker recovery information: Require 48-digit recovery passwordAllow 256-bit recovery key
Omit recovery options from the BitLocker setup wizard Enabled
Save BitLocker recovery information to AD DS for operating system drives Enabled
Configure storage of BitLocker recovery information to AD DS: Store recovery passwords and key packages
Do not enable BitLocker until recovery information is stored to AD DS for operating system drives Disabled

Enter the BIOS on your client or use tools like the Dell client configuration utility to turn on TPM, clear the TPM and activate it. After doing this enable bitlocker encryption on the machine. You can use any method to achive this.

Step 3. Add Bitlocker status to WMI & run hw inventory

Although there are multiple ways of manipulating bitlocker through WMI you still need a script to read, update and store bitlocker status information in the WMI repository (see http://msdn.microsoft.com/en-us/library/aa376409.aspx). This is because Managed Object Format (MOF) files are not installed as part of the Windows SDK and therefore the included classes are not added to the WMI repository automatically by Windows itself.

[update: A handy colleague wrote a powershell version of the script for adding the bitlocker status into WMI with some nice enhancements. All credits go to Daniel Last.]

The scripts (use only one):

  • VBS version: UpdateBitlockerStatus.vbs
  • Powershell verion: Bitlocker_Status.ps1 Bitlocker_Status_v1.1.ps1 [update]

Run the script and after that initiate a hardware inventory on the client. Note that the powershell version of the script already triggers a hardware inventory. Additionally, the powershell script need to be run with the powershell execution policy to be set to RemoteSigned. Do this using the following cmdlet: Set-ExecutionPolicy RemoteSigned

[edit] You could trigger the inventory in the vbscript by adding this line: WshShell.Run “WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule “&Chr(34) & “{00000000-0000-0000-0000-000000000001}” & Chr(34) & ” /NOINTERACTIVE”,,true

After a while you will find 2 new tables and 1 new view in the SCCM site database:

Step 4. Create the Report

I created a report in SCCM with the following query:

SELECT     v_R_System.Name0 AS Computername, v_GS_SCCM_BitLocker0.Bitlocker_Status0 AS [Bitlocker Status],
v_GS_SCCM_BitLocker0.BitLocker_Version0 AS [Bitlocker Versie], v_GS_SCCM_BitLocker0.Conversion_Status0 AS [Converstion Status],
v_GS_SCCM_BitLocker0.Drive0 AS Drive, v_GS_SCCM_BitLocker0.DriveLabel0 AS DriveLabel, v_GS_SCCM_BitLocker0.Encryption_Method0 AS [Encryption Method],
v_GS_SCCM_BitLocker0.Identification_Field0 AS [Identification Field], v_GS_SCCM_BitLocker0.Key_Protectors0 AS [Key Protectors],
v_GS_SCCM_BitLocker0.Percentage_Encrypted0 AS [Percentage Encrypted], v_GS_SCCM_BitLocker0.Protection_Status0 AS [Protection Status],
v_GS_SCCM_BitLocker0.ScriptLastRun0 AS [Script Last Run]
FROM         v_GS_SCCM_BitLocker0 INNER JOIN
v_R_System ON v_GS_SCCM_BitLocker0.ResourceID = v_R_System.ResourceID

And there it is, the Bitlocker report (note: old screenshot based another query but more or less similar):

Tested on SCCM R2 with a Windows 7 Enterprise bitlocker client.

Feel free to comment on this post.

Regards,
Douwe van de Ruit

Read More

VMware ESX3 server running within VMware Workstation 6

Paul Davey from xtravirt wrote a Guide to installing VMware ESX3 on workstation 6.

“This paper illustrates how to install and configure VMware ESX3 Server to run within VMware Workstation 6. From this, VirtualCenter, VMotion, HA and DRS features can be configured.

Although performance is significantly reduced from that of a physical server, this type of environment opens considerable possibilities for portable client demonstrations and is excellent for self training and small lab environments.

This paper assumes the reader has good technical knowledge of VMWare Virtual Infrastructure 3. The paper assumes that you know how to install the VirtualCenter2, License Server and Virtual Infrastructure Client.

The hardware used in this whitepaper was an IBM Thinkpad T60P laptop, Core Duo, 3GB memory, 120GB SATA Hard Disk.

Note: Intel CPU(s) on the hardware running Workstation 6 must have the VT technology or the performance of ESX will be very poor.  It is believed that the same applies with AMD chips with AMD-V compatible CPU’s being recommended, although it is currently untested by us on this platform.”

Read More

Performance impact of Office 2007 on Citrix servers

The Office suite plays a major part in Citrix farms. Not only is it probably the most distributed application suite around, it is also the most used and one of the most resource intensive set of applications on Citrix farms. Maintaining a stable and well performing Citrix farm is probably the greatest concern for every Citrix administrator, so the introduction of a new version of the Office suite will make those eye browses frown of the common Citrix administrator.

Microsoft introduced late 2006 a new Office suite, called Office 2007. Earlier releases of the Office suite always had a significant negative impact on the maximum number of users that were allowed to get access to a Citrix server. So the obvious question to ask is: What is the impact of Office 2007 on a Citrix server compared to Office 2003?. Are we again facing a considerable performance penalty and, if so, how large is this penalty and which specific resources are impacted?

The test

To answer this question we set up a test server (a Dell 1850, 2 (hyperthreated) Intel Xeon 3.2 Ghz with 4 GB of memory) and used the Citrix Server Test Kit to run a number of simple scripts against Office 2003 Standard Edition SP1 and Office 2007 Enterprise Edition.

To be more specific we started 30 user sessions (one session per 2 minutes) and each session did the following:
1. Log on to a Citrix server
2. Start Outlook
3. Start Word
4. Start Excel and perform a number of simple calculations
5. Start Powerpoint, insert a number of slides, type some sentences
6. Wait for 5 minutes and start from step 2 again

We acknowledge the fact that those actions cannot be compared to actual user behavior. However, it does give a quite a good picture of what the performance impact will be.

After some time we logged of 5 sessions, because those 30 sessions already used all the CPU available when using Office 2007. Then we let it run for some time more.

The Result

Now  without further let’s bring in those Resource Manager graphs. The 4 most important ones are right here:

On average some 40 %.

The same graph, but now for Office 2007:

We see an average of 70 %.

Let’s take a look on the processor queue length for Office 2003:

It almost drops down to zero.

The same graph for Office 2007:

Still quite significant!

So what we see from this small test is that Office 2007 consumes way more CPU. If we do a small math:

40% (average 2003 CPU) “ 10% (normal OS CPU) = 30%
70% (average 2007 CPU) “ 10% (normal OS CPU) = 60%

That would make twice as much CPU for Office 2007!

We also checked memory and context switches. Memory consumption was very much the same between the two versions, but context switches was a different story:

Office 2003:

On average 35.000.

Office 2007:

On average 20.000 and more stable. So this shows an opposite result compared to the CPU charts. This time the results are in favor of Office 2007.

The conclusion

Overall this table summarizes the results:

Resource Impact of 2007 compared to 2003
CPU + 100 %
Memory Same
Context switches – 40 %

So what does this mean? It means that for those environments where CPU is the bottleneck the implementation of Office 2007 will definitely mean that you will have fewer users on your existing Citrix servers. How many less? That depends on things like:
• What is the real user behavior? Remember the scripts only perform very basic user actions. Real user behavior may well be different. According to Microsoft Excel 2007 makes more efficient use of the resources available for heavy calculations and those calculations may be finished quicker. So if your users use Excel a lot, the results may differ.
• How many other applications do you make available on your Citrix server? The relative impact of the implementation of 2007 will be less if your users mainly work with other applications.

Here is graph of company that has approximately 80 applications on a Citrix server:

For this customer the CPU consumption of the Office applications combined is more than half of the total CPU demand. Introducing Office 2007 on such a server will decrease the maximum number with a third.

So what if memory is your bottleneck? Will everything be all right then? Only if memory is still your bottleneck after the implementation of Office 2007 and not your CPU. You can easily recognize when CPU is likely to be a bottleneck. Just check your % Processor Time and Processor Queue Length and if it is similar to the graphs below you’re reaching the max of your CPU:

So Office 2007 has a significant impact on the CPU. Will that make SBC as a solution less attractive? Not at all, basically it is IT as we know it. Because together with the higher resource demands we also have higher resources available. 2 years ago a 2 CPU server was the standard, nowadays a 2 duo-core CPU is the standard. What it does mean is that companies should budget for server upgrades just like they do for workstations. Furthermore we have to switch to x64 bit operating systems eventually.

By the way, Office 2007 is at this moment not supported by Citrix!. This link shows the current issues they are having and they intend to have those fixed by mid 2007!

So the information given above combined with your own Resource Manager statistics will make it possible for you to do a decent guess on what to expect when you implement Office 2007. Once you have decided on implementing Office 2007, you probably want to know how to implement 2007. Office 2007 deployment has been revised and there are conversion issues to solve. I will blog on these matters within a few weeks, so keep an eye on this website!

Read More

How to integrate App-V with SCCM without losing the features you care about

One of the most anticipated features of SCCM 2007 R2 is “App-V Integration”. We have recently tested the end-to-end scenario for this integration and we can say with confidence: it BLOWS :-( . In a nutshell, by integrating App-V with SCCM you lose App-V’s best features and reduce the solution to something that’s even worse than SCCM by itself!

So what happens when you enable the App-V/SCCM integration feature in the SCCM Management Console?

  • Control of the App-V client is seized by the SCCM client. If you had App-V running on its own before you enabled the integration, you’ll notice that all App-V apps that are published through App-V’s Publishing Server are now rendered invalid. On launch you’ll get a “Unable to initialize package information (0×00000000)” error.
  • You must now publish your App-V apps through SCCM as “Virtual Application Packages”. This works by importing the .XML file of the App-V package. SCCM will distribute the packages to its Distribution Points and you can enable those Distribution Points for HTTP(S) streaming.
  • To get the App-V apps to your clients, you’ll have to create SCCM advertisements. Basically SCCM advertisements replace the App-V Publishing Server. The behavior of getting App-V apps to your desktop now becomes eerily similar to SCCM’s way of installing applications. No more getting your shortcuts immediately upon logon (like you get with App-V); you will have to go get a cup of coffee and hope that SCCM is willing to give you your apps today.
  • If you created non-mandatory assignments, then you’ll have to go to Add/Remove Programs yourself and click “Run” for all the apps that you want. However clicking “Run” doesn’t actually run your app, it only registers the App-V app with the local App-V client. Don’t expect to see any progress bar or visual feedback that the registration actually happened; just keep scouring around in your Start Menu in hope of finding the shortcuts for your new app.
  • If you created mandatory assignments, you’ll get one or more notifications from SCCM (after some time ofcourse) that SCCM has App-V apps for you that it would like to register with the local App-V client. It will do that on *every* desktop you logon to. Prepare to spend quite a bit of quality time with the SCCM Client…
  • If you’re using either Windows Terminal Services or Fast User Switching in Vista, you’re SOL because the SCCM Client is allergic to terminal sessions. You’ll get a message telling you that “No programs are available to run from a Terminal Services session”. How nice. If you happen to be running the console session, you won’t notice this limitation because at the console session, everything works just fine. So make sure you also test your solution via a terminal session so you won’t get caught by surprise.

 

As a result of the findings described above, we were pretty disappointed with the solution and decided to reverse our decision to integrate App-V with SCCM. However we did like the idea of using SCCM Distribution Points to stream App-V apps from. So we had a go at doing a manual integration of App-V with SCCM so that we could use just the SCCM parts we wanted. The idea was inspired by Tim Mangan’s article which included this diagram:

In his article he never got around to actually testing if it was possible to stream an application that was published by App-V’s Publishing Server from an SCCM Distribution Point. He only verified that is was possible to install the App-V app through an MSI with SCCM. So we ventured to get HTTP streaming working against SCCM Distribution Points, with the shortcuts still being provided by an App-V Publishing Server. In a nutshell: it works! You do have to setup a few mechanisms to get load balancing working though.

Here is how it works:

  • First and foremost: disable the App-V integration with SCCM. To do this, go to the SCCM Console -> Site Database -> Site Management -> <Site> -> Site Settings -> Client Agents -> Advertised Programs Client Agent -> Properties and make sure “Allow virtual application package advertisement” is NOT selected.
  • Enable your SCCM Distribution Points for BITS, HTTP and HTTPS content transfer. To do this, go to the SCCM Console ->Site Database -> Site Management -> <Site> -> Site Settings -> Site Systems -> <your DP> -> ConfigMgr distribution point-> Properties and select “Allow clients to transfer content from this distribution point using BITS, HTTP and HTTPS”.
  • We found that (at least in the RTM version of SCCM 2007 R2) you don’t have to enable “virtual application streaming” on the “Virtual Applications” tab of the distribution point to be able to stream from a SCCM DP when using our manual integration. The added benefit of this is that you can now also use Secondary Site DP’s as streaming servers!
  • Set up an App-V Management Server on any server you like. You can even set it up on a SCCM server, it doesn’t matter. Use the default installation settings for the entire installation. After installation, set the Default Content Path to the following: http://%SFT_SOFTGRIDSERVER%
  • Add an App-V package to SCCM for distribution and streaming:
    • Go to the SCCM Console -> Site Database -> Computer Management -> Software Distribution -> Packages -> New ->Package. Enter the information about your package and click Next. Select “This package contains source files” and set the Source Directory to the location of your App-V package and click Finish. Note that you import the App-V package as a normal SCCM package and NOT as a Virtual Application Package. Importing it as a Virtual Application Package will cause the .SFT file in the App-V package to be renamed and cause the .SFT file to be added to not 1 but 2 locations on each SCCM Distribution Point, doubling storage requirements.
    • When the package is added to SCCM, find the Package ID and use it to update the streaming location in the App-V OSD files. For each OSD file in your App-V package, update the HREF statement to HTTP://%SFT_SOFTGRIDSERVER%/SMS_DP$/SMSPKG/<your SCCM Package ID>/<name of your SFT file>
      (If you are using a File Share Distribution Point, the IIS vdir may be different than SMS_DP$. Verify the vdir name in IIS Manager and ensure that all DP’s are either standard DP’s or File Share DP’s.)
    • Now add some SCCM Distribution Points to your package so that SCCM can distribute the App-V content
  • Import the same App-V package into the App-V Management Server so that you can distribute the shortcuts and set permissions:
    • On the App-V Management Server, go to the App-V Management Console, go to Applications
      -> Import Application and go to the same App-V package folder. Select the .SPRJ file and click Open. Perform your regular App-V import steps and finish the import.
    • The imported applications in the App-V Management Console should now show the correct http:// paths to both the OSD file(s) and the SFT file(s).
  • That’s it! Now just configure your App-V Clients on the desktops to use your newly setup App-V Management Server by configuring a Publishing Server and use Group Policy to set the %SFT_SOFTGRIDSERVER% to the name of a SCCM Distribution Point nearby. We set this variable to DNS name that uses DNS Round Robin to distribute the load to multiple DP’s.
Read More