Tuesday, June 29, 2010

Fix Missing or Corrupt Hal.dll

  1. Boot to the Windows recovery console
  2. get to the proper drive (usually is c:)
  3. type attrib -H c:\boot.ini enter
  4. type attrib -R c:\boot.ini enter
  5. type attrib -S c:\boot.ini enter
  6. type del c:\boot.ini enter (you are deleting the boot.ini this is normally the reason for the corrupt hal.dll)
  7. type bootcfg /rebuild fixboot

After the fix runs reboot and everything should be fixed.  When I first did this I ran into an issue where I got an error "can fixboot on a corrupt registry"  I ran and chkdsk /r after that completed I ran step 7 again and everything worked fine.

I have also heard an alternative solution fix this issue in the recovery console do the following command

Expand D:\I386\HAL.DL_ c:\WINDOWS\SYSTEM32\HAL.DLL

I have never tried this method so I cannot prove it works  but if your issue persists it might be worth a try.  If you get an "access denied" do the attrib command to the HAL.DLL file that might help you. Again I have not tried this method just giving suggestions.

Monday, June 28, 2010

WMI Troubleshooting

This is a great article on troubleshooting WMI issues related to SCCM 2007.

http://blogs.technet.com/b/configmgrteam/archive/2009/05/08/wmi-troubleshooting-tips.aspx

Silent Install Adobe CS3

Copy the entire CS3 software up to a share drive.

Run Setup.exe with --record=1 option run through the install. Copy the 2 files it creates to the same directory as the setup.exe.  Rename them to install.xml and remove.xml.

Create your payload file copy and paste the code below into and notepad and named to "application.xml.override".  Remember to enter your Serial Number.

<?xml version="1.0" encoding="utf-8"?>
<Configuration>
<Payload>
<Data key="Serial" protected="0">serialnumber</Data>
<Data key="Registration">Suppress</Data>
<Data key="EULA">Suppress</Data>
<Data key="Updates">Suppress</Data>
</Payload>
</Configuration>

Then dump that override file into the payloads folder in the folder that ends with  _US_volume

Create your command line for the install
setup.exe --mode=silent --deploymentFile="<DriveLetter>:\<directory containing setup.exe>\install.xml"

CS3 should install silently with no issues.  Exit code 0 means everything installed ok if you get an exit code 7 rerun threw these steps.

Friday, June 25, 2010

Vulnerability Assessments Whats Missed

A friend of mine passed this a long and since I have not had a security post in a while and this is a great article I thought it was worth posting.  Talks about how certain devices on the network like printers, fax machines and security cameras exc are over looked in vulnerability testing.  The article also hits on some other errors in vulnerability testing.

http://www.darkreading.com/vulnerability_management/security/perimeter/showArticle.jhtml?articleID=225700674

Thursday, June 24, 2010

Windows DNS Aging and Scavenging

Had a big DNS problem today and this article really helped me out very detailed and easy to understand.  I have worked with DHCP and DNS in the past never realized how many setting and options there really were to set.  Was interesting you would ping a PC by name and would come back with the wrong IP.  The problem ended up being a combination of short DHCP leases with a long aging and scavenging time set in DNS.

http://searchwindowsserver.techtarget.com/tip/0,289483,sid68_gci1040355,00.html

Tuesday, June 22, 2010

Set Registry Permissions Threw Group Policy

  1. Open Group Policy Management
  2. Edit an existing policy or create a new policy.
  3. Navigate to Computer Configuration ->Policies->Windows Settings -> Security Settings -> Registry.
  4. Right click the Registry and click Add Key.
  5. Choose the Registry key you want to change.
  6. Configure the appropriate permissions.
  7. Choose the proper setting from the Add Object dialog box.
  8. Link or enforce the policy accordingly.

Monday, June 21, 2010

Office 2010 Activation on Captured Image

With the new Microsoft KMS service built into office 2010 you must run the following executable before you can capture your image.

C:\Program Files\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\OSPPREARM.EXE

The reason being is sysprep does not clear out the KMS identifier in Office like it does in Windows.  So every machine will have the same identifier making it impossible for your KMS server to activate your Office 2010 clients.  Run this executable before capturing your image and you should be fine.

Wednesday, June 16, 2010

Computer Associations Problem SCCM 2007

I recently worded on an issue where you would import computers into an imaging collection and it would take hours before they would kick off to image.  I found a Microsoft Hotfix to fix this issue.  Microsoft hotfix KB980270 took care of this issue for me I applied the patch rebooted the server and everything we imported starting imaging.  This issue focus on System Center Configuration Manager 2007 Service Pack 2 but I can tell you from experance SP1 also had the same issue and there was a separate hotfix to fix that issue.

http://support.microsoft.com/?kbid=980270

Tuesday, June 15, 2010

Start System Restore From Command Line

  1. using the task manager click file -> then new task
  2. type cmd this will open a command prompt
  3. then navigate to c:\system32\restore
  4. then type rstrui.exe this should launch the system restore wizard
  5. Now just follow the system restore wizard

Friday, June 11, 2010

Disable Safe Mode

  1. Go to Start> Run
  2. Type regedit and click OK
  3. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SafeBoot
  4. Expand SafeBoot by clicking the + sign and you should see 2 keys with the name Minimal and Network.
  5. Before you can rename the keys you must give yourself permissions to the keys.  Remove inherited right and apply rights to child objects. You many also want to take ownership of the key.
  6. Rename both of the keys to something else, example, Minimal to MinimalX and Network to NetworkX.

Tuesday, June 8, 2010

Thursday, June 3, 2010

Office 2010 Activation

Open a command Prompt as Administrator
Navigate to c:\Program Files\Microsoft Office\Office14 directory or Program Files(x86) if you installed a 32 bit office on a 64 bit PC.
Run the following command to set the KMS server cscript ospp.vbs /sethst:name of KMS server
Run the following command to active office cscript ospp.vbs /act

Office should now be activated remember KMS needs 25 or more Office activation tries before it starts working just FYI

Wednesday, June 2, 2010

Office 2010 KMS Activation Issue

Went to stand up Office 2010 KMS server on an existing 2008 server.  I went to install Office 2010 key management host and I get "Unsupported Operating System".  So I decided to install on 2003 license server again already existing and I get the same error.  I run the key management host on my windows 7 computer thinking maybe I received a bad download runs with no issues.  So after some digging threw office 2010 beta and official release documentation and a few Google searches I found out some very interesting information.  Office 2010 KMS only runs on Windows 2003, Windows 2008 R2 and Windows 7 all other operating systems are not supported.  Microsoft has released a patch to help those still running 2003 KMS server.  But so far no patch for the 2008 server the only fix I have found for that is to upgrade to R2.

http://support.microsoft.com/kb/968915/en-us