Thanks to Eric Moe for the link!
Found this blog, that I found really helps folks understand this multi-use term:
Ran across this capability and wasn’t aware of it. Have any
of you implemented this yet. I have had a couple of customers ask about this
For most, if not all pieces
of content that require distribution to one or many distribution points, we
have the ability to flag ‘Distribute
the content for this package to preferred distribution points’.
In essence if a client requests content that has not already been distributed
to the clients preferred distribution point(s), when this flag is selected,
this content will then be auto-distributed to those preferred distribution
point(s). This could be helpful if you have a large amount of packages that are
only sporadically requested. Instead of populate every distribution point with
every package, let On Demand Distribution figure out an appropriate
distribution pattern. This process is very straight forward however there are a
few gotchas to be aware of specifically around the inclusion of a Fallback
Source DP and/or depending on the purpose of a specific deployment (available /
Interesting the conclusion as well:
When both Fallback DP and On Demand Distribution are
enabled for a deployment, the clients will use Fallback until the On Demand
distribution process has completed for the clients preferred DP.
When using On Demand Distribution and no Fallback, an
available deployment will fail and require manual re-execution once the On
Demand distribution process has completed for the clients preferred DP.
Had this link come across an alias and wanted to share. Thanks!
Great blog post that show a feature by feature comparison.
Below is a good link for details on managing AD RMS in a disaster recovery scenario. Thanks!
Great post with a series of links can be found at the link below:
As I continue to explore great new features that are now available with our latest set of software, this is one which I think folks will find valuable. A great write up on the feature can be found here.
So, is been a couple of years since I have been the blogger I had once been around SharePoint. But with the release of System Center 2012 and the upcoming release of Server 2012 and WIndows 8 pending, I felt it was a great time to start blogging again. For those of you still subscribed, similar to SharePoint, my goal with this blog is to share what I feel are the best links, best resources, and share personal experiences around these technologies. For me, it ends up serving as my personal library of these items, and hopefully for you, it will do the same, or at least help you find the resources you need.
The link above will give you access to the admin folder for non enterprise versions of Office 2010. This is critical to create a silent install (create an msp and place it in the updates folder of the structure). You activite the Office admin tool by "running setup /admin" once you create the admin directory from the download.
This is the link to the steps for Office 2010 and SCCM
One snag I ran into, and knew I needed to set this way but can be lost in all the screens for configuration, is that if you don't state the package does not require the user to be logged on (default), while creating the program for the package in SCCCM, it won't populate when you go to create the install application task sequence (whats funny is we test for this condition but not if you actually checked the "can be called from a task box directly" but I chalk that up to learning :)
Hope this helps folks!
As I continue to dive through challenges for OS Deployment, I keep coming across great links that help me along the way. Wanted to share this one:
Great materials here (also, make sure you check out the pre-reqs before installing, there are quite a few required to ensure a succesful installation.
Virtual Application Management with Microsoft Application Virtualization 4.6 and System Center Configuration Manager 2007 R2
This paper discusses the integration of System Center Configuration Manager 2007 R2 and Microsoft Application Virtualization 4.6, including supported scenarios, best practices, deployment planning considerations, and how to perform common virtual application management tasks with Configuration Manager 2007 R2.
February 22, 2010
Microsoft Application Virtualization 4.6 Sequencing Guide
This white paper is designed to provide administrators with guidance for sequencing applications to create virtual packages that can be delivered to the end user. This white paper discusses setting up the sequencer, sequencing best practices, an example of sequencing, important information related to updating packages, and finally examples of advanced OSD scripting.
February 22, 2010
App-V Application Publishing and Client Interaction
This white paper provides information about how the client operates and where it stores data to support virtual applications.
February 22, 2010
Came across this one while looking for information and think its a great resource that wanted to share.
Turns out permissions are missing.
For each share the document requests you make, you need to add NT Authority\System with Read/Write permissions (Package$ in particular). Found this out through the comments on the deployment guys site (which the original post was to videos you might find interesting)
Hope this helps!