This guide describes how to use System Center Configuration Manager 2012 R2 to import the Windows XP CSA updates.
Logon to the System Center configuration Manager Management point and start the Windows Explorer goto C:\CSA
Remove the ‘old’ files from the Payload directory. Put them in the _Archive folder
Remove the ‘old’ cab file from the ScanCab directory. Put them in the _Archive folder
Download the ‘new’ Microsoft CSA Update Payload Packages to: C:\CSA\Payload And the CAB file to: C:\CSA\ScanCab. Use a Microsoft Account to get access to the Microsoft connect site.
Open a CMD (as an administrator) and change directory to C:\CSA
Excecute the command line: Wsusimporttool.exe c:\CSA\ScanCab\CSA-WindowsXPSP3.CAB c:\CSA\Payload\ c:\CSA\WorkingDir
Reminder: if the wsusimporttool is giving an Error “No instance of WSUS found on this server. WSUSImportTool can only be run locally on a WSUS server” use the WsusUtil from C:\Program Files\Update Services\Tools\ WsusUtil.exe csaimport c:\CSA\ScanCab\CSA-WindowsXPSP3.CAB c:\CSA\Payload
Check if the updates are presented in the database. Start WSUS admin tool and check if the Custom Support updates are added.
Start the SCCM console and goto Administration | Site Configuration | Sites en selecteer de Site kies voor Configure site components | Software Update Point.
Change the settings to do not synchronize from Microsoft Update or upstream data source. Reminder: change these settings back at the end of this procedure
Go to the tab Sync Schedule and choose a date and time which will take place in a couple of minutes.
A new product group, with the name “Windows XP SP3 custom support” will appear. Check this product group. And sync again from the tab sync schedule
Open the wsyncmgr.log to see if the sync is started and when it will be finished.
Wait till it’s finished.
Change the settings back in the Sync Settings Synchronize from Microsoft update
Start the SCCM console and goto Software Library | Software Updates | All Software Updates Click on synchronize Software Updates. Watch the wsyncmgr.log
See if the updates are visible in the SCCM console
If an organization has lots of computers, or if its computers are geographically spread, it’s a good idea to divide its netwerk into smaller ones (subnets) connected by routers. The benefit of using subnets are less traffic (most traffic will stay on the local netwerk) and easier to isolate and identify a network problem.
The subnet mask splits an IPv4 address into a network and a host portion.
In this table below you can see how you can split your subnets using a subnet mask.
Microsoft released a new type of local file system in Windows Server 2012, it is called Resilient File System (ReFS). Microsoft designed this new file system because they see that there is a growth in storage (big data) and it works well with their new Storage Spaces feature in Windows Server 2012.
Initially it will be used for the file servers to prevent data loss and downtime.
In Windows Server 2012 you can choose between FAT32, NTFS and ReFS.
ReFS support features that contain functionality that proactively scans and repairs bad disk clusters (they use a “scrubber”). It’s a “Self-healing” file system and designed to prioritize the availability of data. If data corruption occurs the data will stay available without volume down-time. If data is corrupted an auto-repair (salvage) is triggered (it’s resilient to curruption) and it can remove the corrupted data, the volume will then be brought back online in a split second without the corrupted data.