http://windows.microsoft.com/en-US/windows-8/consumer-preview?ocid=O_MSC_W8P_OandO_ITPro_EN-US
and Windows 8 ITPro portal http://technet.microsoft.com/en-us/windows/hh771457.aspx?ITPID=mscomsc
Wednesday, February 29, 2012
Tuesday, February 14, 2012
BranchCache and Config Manager
BranchCache and Config Manager:
Available only in Windows 7 & 2008
Two Modes: Hosted and Distributed – can be set through group policy -enablement, cache size, bandwidth size
Distribution for Config Manager peer-to-peer download- Requires additional space in clients (Cache Content)- Only within subnet (so each subnet should download once) – clients should be ON for download – content cache security through NTFS ACL.
BranchCache is compatible with VPN software that supports split tunneling
Ports: 80 and 3702.
Firewall: Requires program exception
Available only in Windows 7 & 2008
Two Modes: Hosted and Distributed – can be set through group policy -enablement, cache size, bandwidth size
Distribution for Config Manager peer-to-peer download- Requires additional space in clients (Cache Content)- Only within subnet (so each subnet should download once) – clients should be ON for download – content cache security through NTFS ACL.
BranchCache is compatible with VPN software that supports split tunneling
Ports: 80 and 3702.
Firewall: Requires program exception
Monday, February 6, 2012
Message ID: 8000 -portal Web Site Control Manager detected PORTALWEB is not responding to HTTP requests. Config Manager 2012
If you get this error after SC2012 Config manager application catalog installation, this is due to .NET 4.0.
resolution:
This issue occurs because the Applicationhost.configion catalog file for Windows Process Activation Service (WAS) has the following section defined, and this section is incompatible with the .NET Framework 4.0:
This section should be defined as follows:
Note You can find the Applicationhost.config file in the following location:
%windir%\system32\inetsrv\காண்பிக்
more here: http://support.microsoft.com/kb/2015129
resolution:
This issue occurs because the Applicationhost.configion catalog file for Windows Process Activation Service (WAS) has the following section defined, and this section is incompatible with the .NET Framework 4.0:
This section should be defined as follows:
Note You can find the Applicationhost.config file in the following location:
%windir%\system32\inetsrv\காண்பிக்
more here: http://support.microsoft.com/kb/2015129
Subscribe to:
Posts (Atom)