End of Support of Windows Client Operating Systems
End of Sales of Windows Client Operating Systems
Reference: Windows lifecycle fact sheet
Tag: Windows XP
Configure wake on LAN using system center configuration manager 2007
Click on Start menu, Right Click My computer, Click Manage
OR Start menu>Run>Type devmgmt.msc
Click on Device manager, Expand Network Adapters>Right click on Generic Marvell Yukon chipset based Ethernet controller, Click on property
Click on advanced tab, select Wake From Shutdown, on the right hand side, Set value to on
Click Wake Up capabilities, on the right hand side set value to Magic packet
Click on Power management Tab, check Allow the Computer to turn off this device to save, Allow this device to bring the computer out of standby and only allow management stations to bring the computer out of standby
SCCM Configuration
Configure System center configuration manager 2007
Log on to SCCM server, open ConfigMgr Console, Expand Site management, right click Main site, click on Property
Click on Wake on LAN Tab, Check Enable Wake on LAN, Check Use Power on commands if the computers support technology, Check Unicast. you can select Subnet directed broadcast if your switch support subnet directed broadcast.
Click Port Tab, Select Wake on LAN
To use Wake on LAN functionality, always check Enable Wake on LAN in the schedule of deployment of any software.
There are lots of third party tools you can use to deploy wake on lan such as manageengine, solarwinds and specopssoft wake on lan tools. The painful part of this process would be, in some computer you have to go bios settings and set wake on lan on in power management. If you have dell pc, you can use dell client configuration utilities.
Support for Windows XP SP2,Windows 2000 and Windows Vista ends this year
Windows XP was first released on October 25, 2001 and over 400 million copies were in use in January 2006, according to an estimate in that month by an IDC analyst. It was succeeded by Windows Vista, which was released to volume license customers on November 8, 2006 and worldwide to the general public on January 30, 2007. Direct OEM and retail sales of Windows XP ceased on June 30, 2008. Microsoft continued to sell XP through their System Builders (smaller OEMs who sell assembled computers) program until January 31, 2009. Windows XP may continue to be available as these sources run through their inventory or by purchasing Windows Vista Ultimate or Business and then downgrading to Windows XP.
Updating your Windows 2000, Windows XP and Windows Vista based machine before the end of mainstream support dates will ensure that your machine stay supported and receive security updates. Migrating to Windows 7 provides the longest support lifecycle for your organization helping to ensure protection, support, and timely updates.
Support for Windows Vista RTM ends on April 13, 2010 . To help ensure your Windows Vista PCs stay secure and up to date, make sure they are running Windows Vista Service Pack 1 (SP1) or Service Pack 2 (SP2).
Support for Windows XP SP2 and Windows 2000 ends July 13, 2010. If you are running Windows XP, stay more secure by moving to Windows XP Service Pack 3 (SP3) or migrating to Windows 7.
Microsoft Continuously improve operating systems for their customer. Service Pack, hotfix and Support comes with every operating systems. We are close to finish a chapter. Each phase of technology pass by and leave its legacy. Those who still wants to stay on with Windows XP. Deploy Windows XP SP3 in your organisation to keep it safe and up-to-date. For more information, you may visit Windows Service Pack Road Map and Windows Road Map . That was past and to see the future visit Windows 7 Technical Library Roadmap .
Share this on 
How to configure L2TP IPSec VPN dialler in Windows XP
How to configure Microsoft Radius Server (IAS) for Macintosh OSX 10.5, Windows 7 and windows XP Pro client
Internet Authentication Service (IAS) is the Remote Authentication Dial-in User Service (RADIUS) server in Windows Server 2003 family. As a RADIUS server, IAS performs centralized connection authentication, authorization, and accounting for many types of network access, including wireless and virtual private network (VPN) connections. As a RADIUS proxy, IAS forwards authentication and accounting messages to other RADIUS servers. A RADIUS client (typically an access server such as a dial-up server, VPN server, or wireless access point) sends user credentials and connection parameter information in the form of a RADIUS message to a RADIUS server. Microsoft Radius supports Windows 7, Windows XP SP2 and Mac OSX clients. This article provided an overview of Microsoft RADIUS and PEAP security and described how RADIUS security are implemented and deployed in IT infrastructure.
Prerequisite : Microsoft Active Directory, DNS, DHCP and Certificate Server, Cisco 1200 series wireless AP, MAC OSX 10.5, Windows XP Pro/Windows 7.
AAA Infrastructure:
Aunthentication: Microsoft Active Directory, Authorization: Microsoft Radius (IAS), Accounting: Microsoft Radius (IAS)
Security Measures: PEAP and Shared Secret
Encryption: MSCHAPv2
Configure IAS
Make sure all prerequisites mentioned above are ready and working. Install windows server and make it a member of Microsoft Active Directory domain.
Install machine certificate i.e. computer certificate in this server
Click on add/remove snap in
Click add
Select Certificates, click add
Check computer account radio button, click next
Select local computer, click finish
Right mouse click on personal and click on request certificate, follow screen shot
Click next, then click ok.
Install IAS as follows
Go to Add remove windows component, select internet Authentication Service, click ok.
Open IAS console from administrative tools, right click on IAS as above, click register service in Active Directory
Add RADIUS Client, mention Cisco access point name and IP of Cisco Access Point, click next
Select Radius standard and provide shared secret and confirm, click finish. Shared secret must be same as you mentioned in Cisco wireless access point
Create Wireless access group in windows Active Directory and Add desired members in that group
go to administrative tools in IAS server, open IAS console, Add wireless access policy in Radius server
right click in wireless access policy and create new access policy
Select as above
Check Wireless and click next
Add wireless access group from active directory by click add button
Select PEAP, click on configure
Click ok
Click finish
Now go to property of newly created access policy, click edit profile, click authentication tab, check EAP methods as follows.
Check encryption and authentication method. Use MSCHAP v2. Encryption 128 bits.
Configure Wireless access point as shown in the link
Now infrastructure is ready to authenticate iMac OSX 10.5, Windows 7 and XP via wireless.
Log on to an XP machine using user credentials who is a member of wireless access group. Go to run, type mmc and press ok. follow the steps mentioned above on top to install machine certificate but this time install user certificate i.e. check user account instead of computer account.
Once user certificate installed, right click on user certificate, click All task, click export follow screen shot
Save certificate in usb stick.
Configure Mac OSX 10.5
Now open iMac/Mac book pro. Go to utility, open Key Chain, select login, drag certificate from USB stick and drop it in key chain login, click ok
Type the password used while exporting certificate
go to system preference, open network, select AirPort, click on advance, click on +
Click on show all, select desired Mac wireless SSID, follow screen shot
type AD user name and password who is a member of wireless access group, select certificate, click add
Now authenticated as above. all done.
It is not necessary to bind Mac OSX 10.5 to AD to get wireless authentication via RADIUS. PEAP and certificate will do. now you can add user home drive, printer from print server.
On Windows XP or Windows 7 machine, log on using domain user credential who is a member wireless access group, install user certificate and machine/computer certificate as mentioned above. Turn on wireless, select SSID, click on connect, in few seconds it will be connected.
How to create Admin image of Solidworks 2009 and deploy through GPO or command prompt
you must have solidworks license server installed and running before you prepare admin image.
Step1
Open a Command Prompt window (in Windows, click Start, Run, type cmd, and click OK) and enter:
msiexec /a \\yourserver\solidworks2009\swwi\data\English_i386_SolidWorks.msi
In the SolidWorks Setup Wizard, follow the on-screen instructions.
Step2
Go to the folder that contains the administrative image from Command Prompt window. Type following. The command should be in the format:
\\yourserver\solidworks2009\solidworks\SWCreateMST.exe “\\yourserver\solidworks2009\solidworks\english_i386_SolidWorks.msi” INSTALLDIR=”C:\Program Files\Solidworks” SOLIDWORKSSERIALNUMBER=”xxxx xxxx xxxx xxxx” ADDLOCAL=SolidWorks,English,Manuals,Intel_Modules_AgeiaX86 OFFICEOPTION=0
Here, xxxx-xxxx is serial number. The transform file, English_i386_SolidWorks.mst, is created in the folder that contains the administrative image.
Step3
3. In the Active Directory, edit the Published Apps policy for the group or groups to deploy the SolidWorks software.
4. In the Group Policy dialog box, expand Computer Configuration and Software Settings.
5. Right-click Software installation and select New, Package.
6. Browse to the administrative image and click Open.
7. In the Deploy Software dialog box, select Advanced published or assigned, then click OK.
8. In the SolidWorks Properties dialog box, on the Modifications tab:
a. Click Add.
b. Browse to the .mst file.
c. Click Open.
Click OK.
Command prompt deploy:
msiexec /i \\yourserver\Solidworks2009MSI\Solidworks\English_i386_SolidWorks.msi /qn TRANSFORMS=”\\yourserver\Solidworks2009MSI\Solidworks\English_i386_SolidWorks.mst”
