Brian N. Henry

Professional (Enterprise doesn't seem to be on our MVLS sadly). I can't recall if it joined to the domain at the moment, but I think I did. I had to wipe that VM box to build something else.

I was able to run the Capture CD to create a .wim image for SCCM from a manually installed Windows 7 VM, and even deployed it successfully. However I'm running into a situation where every time the image deploys - it asks for me to create a user account. I'd like to as fully automated on this as possible, any suggestions?

I'm attempting to create a Driver Package on my box (SCCM 2007 R2 with SQL Server 2008 on same box). I put in the name (All Drivers) and the UNC path and click OK. When I do I get the error message: "The ConfigMgr Provider reported an error." Checking my smsprov.log file I see the following entry: [EBC][Fri 07/24/2009 13:07:15]:CExtUserContext: Context Item Name: __GroupOperationId [EBC][Fri 07/24/2009 13:07:15]:CExtUserContext : Context Item Int value: 2693 [EBC][Fri 07/24/2009 13:07:15]:CExtUserContext : Set ThreadLocaleID OK to: 1033 [EBC][Fri 07/24/2009 13:07:15]:CSspClassManager::PreCallAction, dbname=SMS_R13 [EBC][Fri 07/24/2009 13:07:15]:ExecQueryAsync: START Select Count(CI_ID) From SMS_Driver Where ContentSourcePath='\\\\sl-syscenter\\sccm_packages\\driverpack' Or ContentSourcePath='\\\\sl-syscenter\\sccm_packages\\driverpack\\' [EBC][Fri 07/24/2009 13:07:15]:Adding Handle 26144132 to async call map [EBC][Fri 07/24/2009 13:07:15]:CExtProviderClassObject::DoCreateInstanceEnumAsync (SMS_Query) [EBC][Fri 07/24/2009 13:07:15]:CSspClassManager::ReadAccountFromRegistry, Getting NT Service account... [EBC][Fri 07/24/2009 13:07:15]:Using SMS SERVICE Account for impersonation [EBC][Fri 07/24/2009 13:07:15]:SMS ACCOUNT WORK SUCCEEDED [EBC][Fri 07/24/2009 13:07:15]:CSspQueryForObject :: Execute... [EBC][Fri 07/24/2009 13:07:15]:Execute WQL =Select Count(CI_ID) From SMS_Driver Where ContentSourcePath='\\\\sl-syscenter\\sccm_packages\\driverpack' Or ContentSourcePath='\\\\sl-syscenter\\sccm_packages\\driverpack\\' [EBC][Fri 07/24/2009 13:07:15]:Execute SQL =select count ( SMS_Driver.CI_ID ) from fn_ListDriverCIs(1033) AS SMS_Driver where (SMS_Driver.ContentSourcePath = "\\sl-syscenter\sccm_packages\driverpack" OR SMS_Driver.ContentSourcePath = "\\sl-syscenter\sccm_packages\driverpack\") [EBC][Fri 07/24/2009 13:07:16]:Results returned: 0 of -1 [EBC][Fri 07/24/2009 13:07:17]:Removing Handle 26144132 from async call map [EBC][Fri 07/24/2009 13:07:17]:ExecQueryAsync: COMPLETE Select Count(CI_ID) From SMS_Driver Where ContentSourcePath='\\\\sl-syscenter\\sccm_packages\\driverpack' Or ContentSourcePath='\\\\sl-syscenter\\sccm_packages\\driverpack\\' [EBC][Fri 07/24/2009 13:07:17]:CExtUserContext::LeaveThread : Releasing IWbemContextPtr=51490704 Site system status is completely green. I have a few Warnings in components, but most those are from where I accidentally destroyed my previous SCCM server and things are still trying to recover.

Sorry for the long delay - life & App-V jumped in priority. At the time I posted that, on the ConfigMgr Software Update Service which was due to the fact the server was temporarily down. Other than that everything is green.

Sorry mate - got wrapped up on another project. It was a clean install and remote desktop was the only issue I have noticed - I hadn't tried any other features until after I installed the WINS. Site status is showing some green right now.

Nope - the machine names are quite unique across the domain. The format is building hyphen room number hyphen username, so my own is sl-r33-bhenry. When we have users with names like Faulkenberg in room A06B things get tricky. I did however figure out a workaround if not a fix - I enabled WINS through DHCP and release/renewed both the machine I was having issues on as well as my own, plus set it statically on the SCCM box. What puzzles me is why this happened even though the schema is extended. Its more academic now but hey - any answer is a good one.

I'm using SCCM 2007 and largely its working fine but I am running into one issue. Our organization uses a naming scheme for its systems that have resulted in rather long system names. It seems System Center is using the truncated NetBIOS name for the system rather than the full system name, even though it stores it in Resource Names[0]. This is mostly causing issue for my remote control, but I would wager it will cause issues as I move forward with inventory and software distribution. Any suggestions to fix or work around this behavior?