Vicmon

josharldt hit it on the money. Worked for me! Hope this helps someone else.

Thank you josharldt! I will test it out and post results. Have a good one.

Trying to create a collection that will automatically query and update based on users in an OU. Would like to set it up so we can add more queries that will populate users from other OUs as well. Will help with software distribution after training. as well as when users are moved base on new job position. Thank you for any help!

We used Quest AD Migrator tool.

Gogan, If you have installed VAMT 2 onto the server running KMS, you can add the product keys for Win7 and Office 2010 under the 'Product Keys' listing in the VAMT console. Hope this helps. New Bitmap Image.bmp

Attempting to install vNext Beta 2. Using Win2008 R2 x64 Ent. as OS, installed SQL 2008 SP1 CU 10, and all prereqs. Goes to install and then errors out. Here is what the log shows: Cannot copy D:\SMSSETUP\bin\x64\Microsoft.ConfigurationManager.ReplicationConfigurationAndMonitoring.dll to e:\program files\microsoft configuration manager\bin\x64\microsoft.configurationmanager.replicationconfigurationandmonitoring.dll, Win32 error = 2 I have tried this a few times, with different downloads of the Beta and location changes, but to no avail. The account installing is a local admin, as is the server itself. It is joined to the test domain, System management created and delegated control to server. Any ideas?

Still trying to get it to work without issue. Now trying to have driver information as part of image. Putting extracted drivers in a folder on the workstation being imaged, and updateing sysprep with information. Here is what is shown in the readme for the storage driver: extract the driver files: c:\setup.exe -a -pc:\<path> -----I did it a little different--> c:\setup.exe -a -p "C:\6930 Network" Insert the lines below into the UNATTEND.TXT (sysprep) file [MassStorageDrivers] "Intel® 82801IR/IO SATA AHCI Controller" = OEM [OEMBootFiles] iaAhci.inf iaStor.sys iaAhci.cat Txtsetup.oem ::::::: I will post more after results. Peace out cyberspace!

Hello, I am working on a general image with Driver packages for various computer models. I am having a lockup issue with the HP Elitebook 6930p. When I image the laptop, it locks up at the point where it says 'Windows XP Setup Please wait...' When I force a restart, it continues with the image installation without further issue. I am trying to see why it is locking up. I am using the Intel® ICH9M-E/M SATA AHCI Controller for the Driver package. The Driver selected is ESB2 SAST AHCI Controller, and Model is ICH9M-E/M SATA AHCI Controller. I chose this model as it is what I saw listed when checking the Device ID (Ven_8086&DEV_2928 for Storage Controller 1 and VEN_8086&DEV_292D for Storage Controller 2). I had actually setup every AHCI and RAID controller in the driver package to make sure the correct one was applied. MSI Query for driver package: select * from Win32_PNPEntity where PNPDeviceID like "%VEN_8086&DEV_2929%" I pulled the driver from the HP site (sp48491). SCCM is Version: 4.00.6487.2000, on Server 2008 x64 Enterprise. Any direction is appreciated. I promise to post any helpful information for any future lookers.

Reset Boot Image for x86 and it worked. Not sure why the win7 boot image stopped working, but deleting it and just using the default boot image worked for me. Hope this helps someone.

Hello, This is one of the major things work has me wanting to figure out as well. I have tested and found that there are programs that normally do not run in Windows 7 that are able to run when done through App-V. Seems like App-V is creating a nice bubble of any registry settings and file/folders needed when the software is installed on the App-V machine(XP). I create the virtual apps and then push them out via SCCM (awesome guide on how to do that at this website). I am doing more testing, as there are some programs that are 'legacy' and necessary that do not work with Win7. Anyone know of a good detailed manual to configuring App-V client software? Would like to better acquaint myself with how to create shortcuts and configure specifics. Cheers.

Using OEM boot image for Windows 7 Enterprise x86. OS Image Package taken from same iso that was pulled to the server. Installed new boot image from iso image downloaded from MS. Created new TS for B&C and use the boot.wim and folder from known working Win7 iso. Left out cd key, left local admin disabled, and took default on all other screens. Initiate Task Sequence Media Wizard and select stand-alone media. USB flash drive choice of media, as well as setting up advertisement for PXE boot test. One thing to note is that the Advertisment status for the Win7 B&C never shows any recieved, failures, or anything beyond the initial setup of the advertisment. ------------- Severity Type Site code Date / Time System Component Message ID Description Information Milestone QUT 4/26/2010 8:55:20 AM SCCM-Server SMS_OFFER_MANAGER 3900 SMS Offer Manager successfully processed new advertisement B&C Win7. Information Audit QUT 4/26/2010 8:55:01 AM TestSCCM Microsoft.ConfigurationManagement.dll 30006 User "domain\me" created an advertisement named "B&C Win7" (QUT20008) advertising program "*". ------------- SMSTS.log file not on client computer, as it seems to never get to intial SCCM screen. I searched client for sms* and came up empty. I read the troubleshooting article on using F8 for testing, but no success in getting that elusive SMSTS.log file. Thank you for your response.

SCCM 2007 Server: OS Server 2008, SCCM R2 SP2 I am trying to use OSD and have hit a brick wall. Whether through PXE or USB stick, i receive the same error when trying to push out a Win 7 OS. I have MDT 2010, and have reinstalled that and WDS multiple times. PXE has been removed and put back in the same number of times. The error comes up after the unknown computer connects to the server and pulls the wim file. It gets to the screen where you see the shifting bar (looks like KITT or the bad dudes from Battlestar Galactica). After that I receive the following: ---------------- Error Windows PE cannot start because the actual SYSTEMROOT directory (X:\WINDOWS) is different from the configured one (X:\$windows.~bt\Windows). This can be configured from dism.exe with the /set-targetpath command. Please consult the documentation for more details. Press the OK button or close this message to reboot. ---------------- I have to force a shutdown of the computer, as there is nor response from mouse or keyboard to click the OK button. I have checked the client computer and am unable to find the Smsts.log. I haven't found anything on the server as well. Since it doesn't even load the screen to login password and intitiate image push, i see no errors. This message happens for capture as well as push. The account is domain admin and all rights are properlya ssinged (that I know of). Any help is truly appreciated as I am going nuts!!!!!

I have the same issue. I am running SCCM 2007 R2 SP2 on Windows Server 2008. Installed WAIK 2010, WDS, and then PXE Role. Keep receiving that message when trying to add the boot.wim from the Vista source folder taken from the installation DVD. I have gone through the process of uninstalling/removing the PXE Role and WDS, and then installing WDS and then PXE Role, to no avail. Any suggestions? This is a stumper for me. Thank you for any assist. This website has been instrumental in my implementating SCCM at work. The guides are awesome!