| We would like to make you aware of important news regarding certain versions of Windows that could affect your computers and servers. On July 13, Microsoft support—including the release of new security updates—will end for Windows XP Service Pack 2 (SP2), Windows 2000 Server and Windows 2000 Professional. It is also important to note that support for Windows Vista Release to Manufacturing (or RTM, as it is commonly referred to, which indicates the original version without any service packs installed) ended on April 13. |
|
| KEY DATES |
|
| Product |
End of Support (EOS) Date |
| Windows Vista RTM |
April 13, 2010 |
Windows XP SP2
Windows 2000 Professional
Windows 2000 Server |
July 13, 2010 |
|
| WHAT DOES THIS MEAN FOR YOU? |
|
| • |
Microsoft will stop providing incident support and will not release new updates, including security updates. |
| • |
Running an unsupported version of Windows could be harder to manage, expensive to maintain, and could expose your business and your customers to business and regulatory risks. |
| • |
Running an unsupported version of Windows could represent a security threat—Microsoft will no longer release new security updates for vulnerabilities discovered after EOS. |
|
| WHAT SHOULD YOU DO? |
|
| 1) Upgrade to the latest version of the operating system |
|
| Windows 7 and Windows Server 2008 R2 provide you with platforms designed to address the current business and security environment. |
|
| 2) Install the most current service pack |
|
| If you have computers that are not ready to move to Windows 7, then apply the most current service pack to continue to receive updates and support. |
|
| • |
For Windows Vista support and updates, apply Service Pack 2. |
| • |
For Windows XP support and updates, apply Service Pack 3 (SP3). |
| • |
If you have Premier Support, these benefits can be used toward Windows XP SP3 migration and patch management. |
| • |
There are no service pack upgrade options for Windows 2000 Server or Windows 2000 Professional. |
|
| To learn more about your end-of-support options, contact your Microsoft Certified Partner, or visit windows.microsoft.com/eos. |
July 12, 2010 | Categories: Alerts and News | Leave a comment
Issue
To reset the default AutoCAD® MEP 2008 user settings, you want to reinitiate the secondary installer.
Solution
To reset the AutoCAD MEP 2008 default user settings, you must first delete your application files and registry entries for the program. Follow these steps:
Note: Make sure that you back up any customized AutoCAD MEP 2008 files before starting this procedure. CLICK HERE FOR STEPS
1. Log on to the workstation as the user.
2. On the Start menu (Windows), click Run.
3. In the Run dialog box, enter regedit.
4. In the Registry Editor, locate the following subkey and delete it:
HKEY_CURRENT_USER\Software\Autodesk\AutoCAD\R17.1\ACAD-6006:409
5. Exit the Registry Editor.
In Windows Explorer, locate and delete the following application folders:
XP:
C:\Documents and Settings\\Application Data\Autodesk\ ACD-MEP 2008 (Copy and Paste this as a backup)
C:\Documents and Settings\\Local Settings\Application Data\Autodesk\ ACD-MEP 2008
VISTA:
C:\Users\\AppData\Roaming\Autodesk\ ACD-MEP 2008 (Copy and Paste this as a backup)
C:\Users\\AppData\Local\Autodesk\ ACD-MEP 2008
The user should now be able to launch AutoCAD MEP 2008. When the product is opened, the files and folders that were deleted will be recreated by the secondary installer.
Warning! Problems caused by improperly editing the Windows registry could render your computer operating system unusable. Microsoft provides a wealth of critical information that you need to know about the registry in the Microsoft Knowledge Base at http://support.microsoft.com/support.
Use the Microsoft® Registry Editor only at your own risk and only after backing up the registry as well as the system.dat and user.dat files as outlined for your operating system in the Microsoft Knowledge Base and in the related solution, TS66513. Additional information about the registry is also contained in the Help topics in the Microsoft Registry Editor.
July 12, 2010 | Categories: Secondary Installers | Leave a comment
Tech Solutions 