Installing .net framework v1.1 on Vista

Installing .net framework v1.1 on Vista



Best Practice importing drivers in SCCM

Best Practice importing drivers in SCCM

What would be the required best practice steps on how to import new drivers in System Center Configuration Manager (SCCM), when building a new hardware model.
Kenny Buntinx introduced a good series of articles discussing on this issue.

SCCM 2007 : Best Practice importing drivers (Part 1) , creating a driver Package.

SCCM 2007 : Best Practice importing drivers (Part 2) , importing a driver into the SCCM Database.

SCCM 2007 : Best Practice importing drivers (Part 3) , Creating your search folders in SCCM.

SCCM 2007 : Best Practice importing drivers (Part 4) , adding drivers to your SCCM Driver Package.

SCCM 2007, WinXP deployment sound card problem

SCCM 2007 : Solution for audio issue when building your Windows XP SP3 Reference image
By Kenny Buntinx

When you deploy a Windows XP SP3 reference image, and you use the Task Sequence to add certain soundcard drivers you might face the problem that your soundcard drivers are installed but at the end there is no sound.

Apparently if you do not log in without a user on your XP SP3 windows can't detect a part of the soundcard device.

A possible solution is installing the sound device manually and using the application drivermax (http://www.innovative-sol.com/drivermax/) to capture the necessary drivers.

Import these drivers as a driver package in SCCM and deploy it with your task sequence.

Guidelines to build a greadt virtual machine

Building a great Virtual Machine
By Kim Oppalfens

Domain Name and Passwords should be keyboard agnostic (ie: be the same on azerty/querty )

  • Domain Example: Contoso.net
  • Password Example: Topsecret

The lab layout should be set as the background image, like in the screenshot

The lab should contain the lab credentials set with bginfo

The saved parameters file and the windows background should be saved to a folder called c:\bginfo

Create login script with saved bginfo parameters file to run as login script.

The machine should allow you to shutdown/ restart from the ctrl-alt-del box

The welcome page should be disabled

System restore should be disabled

The shutdown event tracker should be disabled

password complexity should be disabled

Changing the computer account password should be disabled.

Screensaver should be disabled

Showing icons on the desktop should be disabled (you didn't spend all this time on building backgrounds to have them cluttered with icons)

All passwords should be configured to not expire

Vm's should be running on the latest service pack

Your last login should be with the user that the people will need in the lab so that it is prefilled when pressing ctrl-alt-del

the c:\drive should contain a folder called buildguide and an rtf file with the steps taken to create the vm, this way you can see what preparative action has been taken to make the labs work.

So I created my lab environment in visio and saved the different visio's as bmp's

And set a lot of the above options using a gpo, I backupped the gpo and saved it. The gpo can be found here:http://scug.be/files/folders/sccm/default.aspx

And you could obviously import it back on any domain controller using gpmc.

SCCM2007 OSD : Customising your Task Sequence for Building a Client OS on your VMWare Workstation 6.0 or later
By Kenny Buntinx

This article provides detailed steps on how to build a reference image of your physical workstations onto your VMware Workstation so that people could play around


Deploying a Windows XP SP3 "Gold image" with SCCM 2007

Deploying a Windows XP SP3 "Gold image" with SCCM 2007

By Kenny Buntinx


This post and subsequent posts will be a step by step on how to build a base XP SP3 image in SCCM. I will be outlining not necessarily pointing out every click. Hopefully others will find this helpful. This assumes an understanding of SCCM and uses what is referred to as a “Thin Image Strategy”.

1.Create a network access account, it only need be a domain user and its password should not expire. Add the account to the Computer Client Agent in the Client node under Site Settings

2. Import XP SP3 as an operating system Install Package.

3. Add a Distribution point to your new XP SP3 package created in step 1

4. Create the XP SP3 sysprep package in SCCM

4.1 The Deploy.cab included on the CD was not updated properly for XP SP3 so you must download a new version here.

4.2 Create a package that points at the extracted CAB file for its source

4.3 You do not need to create any programs for the package the build task sequence takes care of this

4.4 Add the package to a DP that can be used during your build

5. Create a package for the Config Mgr Client

5.1 Specify always obtain file from source directory

5.2 Usually here I create a share at \\SCCMSERVER\Souce$\SCCMClient.

5.3 Update the ccmsetup command line properties accordingly. Extensive information about command line properties on TechNet here.

5.4 Add the package to a DP that can be used during your build

6. Create a “Build and capture a reference operating system image” task sequence

6.1 Name the task sequence something appropriate like “Build & Capture Windows XP SP3 Gold 6.2 Image”

6.3 Select the x86 boot image

6.4 Select the Operating System Package you created in step 1

6.5 Enter a product key

6.6 Set the local admin password to any password

6.7 Join a workgroup

6.8 Select the Config Mgr client you created in step 4

6.9 Don’t add any software to the base image

6.10 Set your image properties

6.11 Select a location to save the image and make sure you include the full path including the .wim extension

6.12 Enter an account with rights to write to the share

6.13 Finish up

7. Change the task sequence to use “Quick Format”

7.1 Right Click on the Task Sequence and choose Edit

7.2 Select the “Partition Disk 0″ step

7.3 Choose properties on the Default (Primary) partition and check the “Quick Format” option

8. Create a collection to which you will advertise the task sequence; I usually use "customer" Base Builds

9. Advertise the task sequence to the collection you created in step 7 as optional

9.1 Right click Task sequence and choose advertise, follow the wizard

9.2 Make sure you select the check box “Make this task sequence available to boot media and PXE”

9.3 If you are in test and your boundaries are not defined make sure you select “When no local distribution points are available, use remote distribution point”

9.4 Make sure you completed step 1

10. Ensure that you have the network and mass storage drivers to boot the device on the boot image and in the driver store (If you have to do this in the future you must update the PXE and standard DPs)

11. Add the appropriate boot images (x86 / x64) to the PXE and standard DPs

12. Allow the client to boot from PXE

12.1 If this client previously had an SCCM agent on it you just need to add the client to the collection you created in step 6

12.2 If this is a new client and SCCM is pre-R2 add the client manually

12.2.1 Add the client by right clicking the Computer Associations node under OSD and choosing “Import Computer Information”

12.2.2 Enter the Name of the computer

12.2.3 Enter the MAC and or SMBIOS GUID

12.2.4 Add the computer to the collection you created in step 7

13. Boot the device up to PXE and choose your task sequence. In less than an hour you should have the start of a great XP Image

SCCM OSD Deployment with static IP address

SCCM OSD Deployment with static IP address

Deploy a new system via SCCM OSD, there is no DHCP in the LAN, hence have to setup static IP on the workstation.
But the problem is, the static IP lost after reboot the workstation.


When there is no DHCP, the manually typed IP settings will gone after reboot if you don't fill the data again, becasue TS variables are just created as OS environment variables.

To resolve this, you can add 'Apply Network settings' step in task sequence

Then write a custom script using the SMS.TSEnvironment COM object to set the TS variables to get this done.

Apply Network Settings Task Sequence Action Variables

How to Use Task Sequence Variables in a Running Configuration Manager Task Sequence

SCCM: OSD Task Sequence fails to join the PC to the domain during system build

ConfigMgr 2007: OSD Task Sequence fails to join the PC to the domain during Windows setup

Issue: When running a SCCM 2007 OSD Task Sequence deployment to a PC, the PC will be successfully download the image, however when it runs through Windows Setup, the PC will eventually fail to join the domain and the Task Sequence will fail. Inspecting the "Apply Network Settings" task in the Task Sequence shows that all settings and accounts being used in the task are correct.

Looking at the SMSTS.log, the following error message will be repeat throughout the log:

Sending StatusMessage
Formatted header:

CLibSMSMessageWinHttpTransport::Send: URL: :80 CCM_POST /ccm_system/request
Error. Received 0x80072ee7 from WinHttpSendRequest.
unknown host (gethostbyname failed)
hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)
sending with winhttp failed; 80072ee7
Will retry in 5 second(s)
CLibSMSMessageWinHttpTransport::Send: URL: :80 CCM_POST /ccm_system/request
Error. Received 0x80072ee7 from WinHttpSendRequest.
unknown host (gethostbyname failed)
hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)
sending with winhttp failed; 80072ee7
Will retry in 10 second(s)
CLibSMSMessageWinHttpTransport::Send: URL: :80 CCM_POST /ccm_system/request
Error. Received 0x80072ee7 from WinHttpSendRequest.
unknown host (gethostbyname failed)
hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)
sending with winhttp failed; 80072ee7
Will retry in 22 second(s)
CLibSMSMessageWinHttpTransport::Send: URL: :80 CCM_POST /ccm_system/request
Error. Received 0x80072ee7 from WinHttpSendRequest.
unknown host (gethostbyname failed)
hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)
sending with winhttp failed; 80072ee7
Will retry in 45 second(s)
CLibSMSMessageWinHttpTransport::Send: URL: :80 CCM_POST /ccm_system/request
Error. Received 0x80072ee7 from WinHttpSendRequest.
unknown host (gethostbyname failed)
hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)
sending with winhttp failed; 80072ee7
End of retries
Send (pReply, nReplySize), HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,2052)
failed to send the request
DoRequest (sReply, false), HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,3835)
Failed to send status message (80072ee7)
smStatusMessage.Send(), HRESULT=80072ee7 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\utility.cxx,529)

Cause: This is caused by a missing NIC driver in the Windows installation. Either the NIC driver was missing or not available during the driver injection (Apply Device Drivers, Auto Apply Drivers, or Apply Driver Package tasks) of the Task Sequence and driver installation portion of Windows Setup. Because of this reason, the PC has no network connectivity, cannot join the domain, and the Task Sequence eventually fails. However, a NIC driver was present as part of the WinPE Boot Image, which allowed the deployment to get far along enough in the deployment process where it dropped the image down on the PC.

Resolution: To correct the problem follow the steps below:

1) Make sure that the appropriate NIC drivers for the model PC, Windows OS version, and architecture have been imported into the Operating System Deployment --> Drivers node in the SCCM 2007 Admin console.

2) Make sure that the imported NIC drivers from step 1 have been added to a Driver Package under the Operating System Deployment --> Driver Packages node in the SCCM 2007 Admin console.

3) Make sure that the Driver Package from step 2 has been copied to distribution points (DPs) that are accessible to the PC during the OSD Task Sequence deployment.

4) If using the "Apply Driver Package" task in the Task Sequence, make sure that Driver Package that contains the NIC driver is selected in the "Apply Driver Package" task next to the field "Driver Package". If filtering Driver Package by model using WMI queries under the Options tab of the "Apply Driver Package" task, ensure that the WMI query is correct and you choose the correct model PC.

Enable portfast on CISCO switch to fix SCCM error 0x80072ee7

ConfigMgr 2007: Task Sequence may fail to run with error code 0x80072ee7

If you're PXE booting machines and they're throwing 0x80072ee7 errors along with getting APIPA addresses then you might try turning on portfast if you're using a Cisco Spanning Tree Protocol (STP) enabled switch to see if that helps:

Issue: When attempting to PXE Boot and install an OS Image with SCCM 2007, the Task Sequence may error out and reboot the machine. The SMSTS.LOG files may show error code 0x80072ee7 that points to a name resolution and/or networking issue. Additionally, you may notice that WINPE boots and gets an IP address from the DHCP server initially, however, once it gets to the Graphical User Interface portion of WINPE and try and run the Task Sequence it reverts to an Automatic Private IP Address (APIPA) of 169.354.x.x.

Note: If you use Task Sequence Boot Media and manually configure a static IP address and subnet mask, etc. then the Task Sequence runs as expected.

Cause: This can occur if portfast is not enabled on your SPT enable Cisco switch. If portfast is not enabled then the port using STP may remain in blocking mode long enough to prevent the client computer from communicating over the network.

Resolution: To resolve this issue you can turn on "spanning tree portfast enable" on the Cisco switch. For more information on this feature contact your switch manufacturer or see the following article on Cisco.com's website:



TechNet Virtual Labs: Windows System Administration Scripting

TechNet Virtual Labs: Windows System Administration Scripting http://technet.microsoft.com/en-au/virtuallabs/bb512930.aspx

Step into the Windows Scripting Virtual Labs for Free

It's simple: no complex setup or installation is required to try out Windows System Administration Scripting running in the full-featured TechNet Virtual Lab. You get a downloadable manual and a 90-minute block of time for each module. You can sign up for additional 90-minute blocks any time.

Virtual labs
TechNet Virtual Lab: Using Microsoft Windows PowerShell for Administration and Customization of Microsoft Windows SharePoint Services 3.0
TechNet Virtual Lab: Writing Scripts with Windows Powershell
TechNet Virtual Lab: Using PowerShell in Windows Server 2008 Beta 3
TechNet Virtual Lab: Introduction to Windows PowerShell
TechNet Virtual Lab: System Administration Scripting
TechNet Virtual Lab: Active Directory Scripting
VBScript tools for windows

Contents of Guy's VBScript Tool Kit
ADSI - Check LDAP properties
Cacls - Set permissions
Connections web site
CDVDE - Bulk import / export accounts
LDIFDE - Bulk import / export accounts
Link Checker
NetSh - Network Shell
OH (Open Handles)
StringConverter.exe - LDIFDE Password generator
Windiff - Compares two files
WSH client for Windows 9x and NT 4.0
VBScript tools for windows

Contents of Guy's VBScript Tool Kit
ADSI - Check LDAP properties
Cacls - Set permissions
Connections web site
CDVDE - Bulk import / export accounts
LDIFDE - Bulk import / export accounts
Link Checker
NetSh - Network Shell
OH (Open Handles)
StringConverter.exe - LDIFDE Password generator
Windiff - Compares two files
WSH client for Windows 9x and NT 4.0

ADSI Scriptomatic

ADSI Scriptomatic

What is the ADSI Scriptomatic?
The ADSI Scriptomatic -- as we keep trying to tell you -- is designed to help you write ADSI scripts; that is, scripts that can be used to manage Active Directory. As if that isn’t enough (and we learned the hard way that things are never enough), the ADSI Scriptomatic also teaches you an important point about ADSI scripting: like WMI, there are consistent patterns to ADSI scripts. For example, the ADSI Scriptomatic will help you write a script to delete a user account. It will also help you write scripts for deleting groups and organizational units. And if you take a close look at the scripts for deleting different objects, you’ll see something very interesting: theyre practical identical! What is this, some kind of a rip-off?

Well, it might be. But the reason the scripts look so similar is because ADSI uses a consistent approach for deleting objects, regardless of the type of object being deleted. What does that mean? Well, if you take the time to study the scripts created by the ADSI Scriptomatic (and if you read the ADSI chapter from the Windows 2000 Scripting Guide), you’ll understand how you can delete pretty much anything from Active Directory. For example, we wanted to keep the ADSI Scriptomatic relatively simple; as a result, weve limited the objects you can work with. The ADSI Scriptomatic will write a script that deletes a user account, but it won’t write a script that deletes a published printer. But, hey, so what? After you understand the pattern, you can write your own script for deleting published printers. (OK, OK, well consider creating the DeletePublishedPrintersOmatic. But don’t hold your breath.)

Find for details from here:

Download ADSI Scriptomatic

Take Advantage of Scriptomatic 2.0 to Maximize Your WMI Scripting Efforts

Scriptomatic 2.0 resources

Take Advantage of Scriptomatic 2.0 to Maximize Your WMI Scripting Efforts

The simplest and most obvious use for Scriptomatic is reading and displaying a class's properties and their values. When Scriptomatic 2.0 loads, it defaults to the root\CIMV2 namespace, then loads the classes in that namespace. You select a WMI class, such as Win32_ComputerSystem, to generate a script.

After Scriptomatic 2.0 generates the code, you can immediately run the script or save it to a file so that you can use it to create more complex code. If you run the script, you can output the results as command output in the command-shell window, as a text file for viewing in Notepad or another editor, as an HTML or XML file for viewing in a browser such as Microsoft Internet Explorer (IE), or as a comma-separated value (CSV) file for viewing in Microsoft Excel or another spreadsheet program.

Scriptomatic 2.0 alone won't give you a complete picture, which is why you need several WMI-specific tools and references in your toolkit. Here's a list of essential WMI tools and documentation that you can use to expand on the information Scriptomatic 2.0 provides:

Using Contrast as an Effective Learning Tool

Scriptomatic 2.0 lets you select other WMI namespaces besides the common root\CIMV2 namespace. CIMV2 is the only namespace available in version 1.0. In version 2.0, you can gain insight on whether a namespace (i.e., provider) is available on other platforms. For example, the root\MicrosoftIISv2 provider is available on Windows 2003 computers running Microsoft IIS 6.0. In contrast, this namespace isn't available on computers running Windows XP and IIS 5.1 because the MicrosoftIISv2 provider is available only on IIS 6.0.

Download Scriptomatic 2.0:


VB Scripts generated by Scriptmatic, ready for use.

VB Scripts generated by Scriptmatic, ready for use.


VBScript > aspnet(14)
VBScript > CCM\invagt(7)
VBScript > CCM\Policy\Machine(40)
VBScript > CIMV2(495)
VBScript > CIMV2\Applications\Exchange(5)
VBScript > CIMV2\Applications\MicrosoftIE(10)
VBScript > CIMV2\Dell(50)
VBScript > CIMV2\SMS(2)
VBScript > DEFAULT(2)
VBScript > directory\LDAP(3)
VBScript > IntelNCS(38)
VBScript > Microsoft\SqlServer\ComputerManagement(15)
VBScript > MicrosoftActiveDirectory(7)
VBScript > MicrosoftDNS(37)
VBScript > MicrosoftExchangeV2(3)
VBScript > MicrosoftIISv2(337)
VBScript > MicrosoftNLB(20)
VBScript > MOM(14)
VBScript > MSAPPS11(121)
VBScript > perfmon(1)
VBScript > Policy(2)
VBScript > RSOP(2)
VBScript > ServiceModel(80)
VBScript > subscription(1)
VBScript > WMI(378)


Everything About Labels in Blogger.




首先,linux随机启动的服务程序都在/etc/init.d这个文件夹里,里面的文件全部都是脚本文件(脚本程序简单的说就是把要运行的程序写到一个文件里让系统能够按顺序执行,类似windows下的autorun.dat文件),另外在/etc这个文件夹里还有诸如名为rc1.d, rc2.d一直到rc6.d的文件夹,这些都是linux不同的runlevel,我们一般进入的X windows多用户的运行级别是第5级,也就是rc5.d,在这个文件夹下的脚本文件就是运行第5级时要随机启动的服务程序。需要注意的是,在每个rc (1-6).d文件夹下的文件其实都是/etc/init.d文件夹下的文件的一个软连接(类似windows中的快捷方式),也就是说,在 /etc/init.d文件夹下是全部的服务程序,而每个rc(1-6).d只链接它自己启动需要的相应的服务程序!
要启动scim(某一程序),我们首先要知道scim程序在哪里,用locate命令可以找到,scim在/usr/bin/scim这里,其中usr表 示是属于用户的,bin在linux里表示可以执行的程序。这样,我就可以编写一个脚本程序,把它放到/etc/init.d里,然后在rc5.d里做一个相应的软链接就可以了。



Apcupsd a daemon for controlling APC UPSes


Apcupsd can be used for power mangement and controlling most of APC's UPS models on Unix and Windows machines. Apcupsd works with most of APC's Smart-UPS models as well as most simple signalling models such a Back-UPS, and BackUPS-Office. During a power failure, apcupsd will inform the users about the power failure and that a shutdown may occur. If power is not restored, a system shutdown will follow when the battery is exhausted, a timeout (seconds) expires, or runtime expires based on internal APC calculations determined by power consumption rates.



Problems accessing file shares on Windows Server 2008 64-bit running Symantec Endpoint Protection


Network resources on Win2008 serve cannot be accessed after installed SEP 11.0.
This article is the solution.

BTW, don't install Network component if you don't need.

Installing Windows XP on 6710b / SATA Native Mode Issues

It's known that, when install XP on HP 6710b, you must turn off SATA native mode from BIOS first otherwise HDD cannot be detected.

The below is a discussion on how to install WinXP while SATA native mode turned on.

Suggestion from Matthew Neale:
There's an easy fix for getting around the f6 prompt and supplying a floppy disk...

download Nlite http://www.softpedia.com/progDownload/nLite-Download-12443.html

Install Nlite on a pc, run the program, it will prompt for a win xp source disk, then will prompt you to pick a location u want to save it to, the next screen is where we work our magic, have your sata drivers on hand and select integrate -> drivers and the make bootabe cd option... click next, it will prompt you to select the drivers you want to inject into the windows installation cd...

follow the prompts and burn your cd...

you now have a windows xp installation cd with sata support for your 6710b

Verified by Cheryl G.:
Hi Matthew
Yes,Nlite is the best! I found Nlite since this post and recommend it all the time now with the driver and guide below.
Intel SATA driver.
Download and run it,make a floppy OR cancel floppy creation.The files will be extracted to C:\Swsetup\sp37005 to use with Nlite.

Enabling SATA Native Mode after XP Install

You can use Nlite to integrate the drivers into a new XP install cd.Nlite will even burn the new XP cd.
Very easy ,just follow the guide below closely.

Nlite dl:

mikenchi reported an issue with this method
Hi all:
One word of warning. I used nLite and it does cause problems in some cases. If you remove an OS component, then need it later, you cannot add it, and sometimes need to do an OS repair with an original XP cd. Also, it is not compatible with Sysprep. (The author of nLite even acknowledges this) After you sysprep a machine, and apply the image to a new machine, after the first reboot it will pause asking you where are a number of files.