Posts

Powershell to Automate Publishing of Bulk App-V 5.0 or 5.1 packages to a User in a Standalone environment.

In a standalone environment, where there are many App-V 5.0 or App-V 5.1 packages that needs to be published and mounted to a user in order to test the applications, it’s quite hard to open up powershell and type in the commands each time. This is quite time consuming and a repeated job.   With this powershell script, the job can be made easy by publishing these BULK packages. This powershell script code contains commands to ADD the App-V packages along with their respective DeploymentConfig.xml file and Publish them along with their UserConfig.xml file and at last Mount them successfully. User has to first place all the App-V packages in a single folder and then edit the powershell script by giving in the exact folder path.   The powershell code will first load the AppvClient module.   #Import App-V Client Module     Import-Module AppvClient      Next it will enable the execution of scripts present in the dynamic configuration files.  ...

Powershell to Automate Publishing of Bulk App-V 5.0 or 5.1 packages Globally in a Standalone environment

In a standalone environment, where there are many App-V 5.0 or App-V 5.1 packages that needs to be published and mounted in order to test the applications, it’s quite hard to open up powershell and type in the commands each time. This is quite time consuming and a repeated job. With this powershell script, the job can be made easy by publishing these BULK packages. This powershell script code contains commands to ADD the App-V packages along with their respective DeploymentConfig.xml file and Publish them  and at last Mount them successfully. The powershell code will first load the AppvClient module. #Import App-V Client Module Import-Module AppvClient Next it will enable the execution of scripts present in the dynamic configuration files. #Enable execution of scripts Set-AppvClientConfiguration -EnablePackageScripts 1 NOTE: User has to edit the powershell code and give in the exact path where the packages are located. Say example, you have kept all the App-V packages in C:\App-...

Fixed: Importing Windows 10 drivers in ConfigMgr 2012 fails with “Driver is not applicable to any supported platforms. Code 0x80070661”

With the Cumulative Update 1 for System Center 2012 R2 Configuration Manager Service Pack 1 and System Center 2012 Configuration Manager Service Pack 2, Windows 10 drivers can now be successfully imported into the DriverCatalog.log file for operating system deployment. DriverCatalog.log file Information: Initializing driver digest from '\\server\Windows10-x64\{Windows10-driver}.inf'\\server\Windows10-x64\{Windows10-driver}.inf is not applicable to any supported platforms.Driver is not applicable to any supported platforms. Code 0x80070661 This problem was due to the way version number recognition was performed prior to the CU1 update. For more Information click Microsoft link here  

Download Microsoft E-books for free

Download Microsoft E-book for free. Including Windows 10, Windows 8.1, Windows 8, Windows 7, Office 2013, Office 365, SharePoint 2013, Dynamics CRM, PowerShell, Exchange Server, Lync 2013, System Center, Azure, Cloud, SQL Server etc. So why wait, Go and grab your own copy. Download Links: Link1 Link2 Link3

Free ebook: Introducing Windows 10 for IT Professionals, Preview Edition

The Windows 10 Technical Preview offers anyone an opportunity to not just try out the next version of Windows but to provide feedback about the new operating system, in real time, to the team that is building it. Author Name - Ed Bott. Download the book from here

Installing Windows 10 using the media creation tool

The media creation tool can be used to upgrade your current PC to  Windows 10  or to create a USB or DVD and install Windows 10  on a different PC. To download the tool click on the below link. https://www.microsoft.com/en-us/software-download/windows10

Connection Group Overview: Full infrastructure compared to SCCM

Full infrastructure SCCM Connection Groups have to be explicitly published to a target. Only the App-V application sequences have to be distributed to a target. Connection groups are automatically created if a Virtual Environment (VE) is applicable. All App-V sequences in a connection group are available on the target that the connection group has been published to regardless of whether or not the separate sequences have been published to the target. The ability to create ‘AND’ and ‘OR’ VE’s. In the case of an ‘AND’ VE the connection group will be created only when all sequences in the connection group have been distributed to the target. In the case of an ‘OR’ VE the connection group will be created with only the sequences that have been distributed to the target. Connection group priority can be set at the server console.(Although this does not work with App-V 5 Sp1 due to a bug. This bug has been fixed in Hotfix 1 for App-V 5.0 SP1 Management Server...