| WinPE Version | PE Version | Derived From |
|---|---|---|
| WinPE 1.5 | 5.1.x | Win XP SP2 |
| WinPE 2.0 | 6.0.x | Vista |
| WinPE 3.0 | 6.1.7600.16385 | Windows 7 |
| WinPE 4.0 | 6.2.x | Windows 8 |
| WinPE 5.0 | 6.3.x | Windows 8.1 |
| 10.0.10240.16384 | 10.0.10240.16384 | Windows 10 |
What are the Alternatives for Microsoft Load Balancing: below are few which are famous for their brand :)
o F5 Networks
o Barracuda
o Citrix NetScaler
o KEMP
o Cisco ACE
App-V 4.6 | App-V 5.0 | |
| | | |
| Windows XP, Vista, 7 and 8.x desktop OS support | | Windows 7 and 8.x desktop OS support |
| Windows Server 2003, 2008 and 2008 R2 Server OS Support | | Windows Server 2008 R2 and 2012 Server OS Support |
| Dynamic Suite Composition (DSC) | | Connection Groups |
| Primary Virtual Application Directory (PVAD) | | PVAD no longer required prior to sequencing |
| Limited Shell Extension Support | | Extended Shell Extension Support |
| Limited ActiveX Support | | Improved ActiveX Support |
| Shared Read Only Cache | | Shared Content Store |
| .SFT package file format | | .APPV package file format |
| Packages are backwards compatible with earlier versions | | No backward compatibility; Converter Tool or Sequence again. |
| .OSD | | .XML Dynamic Deployment/User Configuration |
| Sfttray.exe for application launch | | Application .exe initiated directly |
| Application reboot simulated by Sequencer | | Application reboot physically actioned during Sequencing |
| RTSPS, RTSP, HTTP, HTTPS and SMB streaming | | HTTP, HTTPS and SMB streaming |
| SFTMIME/SFTTRAY commands on client and SFTSEQUENCER command line for sequencer | | PowerShell commands on client, sequencer and server |
| Q: Drive | | No mount drive on sequencer or client |
| Sftlog.txt and Event Log error reporting | | Moved to Applications and Services Event Logs |
| SFTFS.FSD cache file | | File/Folder structure in %PROGRAMDATA% |
| Default isolation of applications | | Default isolation of application apart from Virtual Application Extensions |
| MMC Management Server Console | | Management Server Silverlight web console |
| ApplicationSourceRoot | | PackageSourceRoot |
Above are the Differences between App-V 4.6 and App-V 5.0
Migration from APP-V 4.6 to 5.0 with SP3
Below are few Models that I have worked last week for hardware integration for SCCM 2012
Model Name MTM number
Lenovo T440p - 20AN
Lenovo T440p - 20Aw
Lenovo X240 - 20AM
Lenovo L440 - 20AS
Lenovo M83 - 10AH
HP DC7900 SFF
Lenovo M58 - 6234AL4
Lenovo M58 - 6234F48
Lenovo X230 - 2324
Lenovo T430 - 2347
Lenovo T430 - 2344
Lenovo M82-2742
Lenovo M82 2929
Lenovo x230 - 2325
Lenovo T430 - 2349
Lenovo W520 (4284-4LG)
Lenovo X220 4291-4CG
Lenovo L440 - 20B7, 20AN, 20AM
Lenovo T440 - 20B7
Lenovo T430 - 2349
Lenovo X230 - 2324 and 2325
How can I Install PnP drivers without Actually installing
How can I setup SCCM to install Drivers automatically / PnP
This is completely out of box from SCCM, as this is nowhere talked about in the documents for SCCM, We actually follow windows default method of *.inf files to install Drivers by using PnpUtil.exe file.
For example if we have Lenovo T440p Model and we wanted to integrate it as a first step we need to copy the Driver to some folder in target system and then while rebooting we can use Pnputil.exe command to install best matching PnP Device Drive drivers from source.
Create T440P model Drivers Source PnP source
And as a next step I have created a basic task sequence and added a step called Copy Drivers to Locally to C:\Drivers Folders
Copy all the drivers to a local driver
xcopy.exe ".\*.*" "c:\Drivers\" /D /E /C /I /Q /H /R /Y /S
Final step would be call a batch file with help of for command, after SCCM client installing step. See below
Below is the impdrv.cmd file
forfiles /p %1 /s /m *.inf /c "cmd /c pnputil -a @Path"
Ofcourse there are multiple ways, and this is one of the option.
