Jeff K

i am going to try getting the machine rebooted sometime this week. see if this helps or hinders the installation

the other question i have is if i take the wsus gpo now and point it to the sccm server will that automatically update all clients to go there and install the sup installation if turned on?

ok i have multiple forests and domains. i have wsus servers in each. we now have all clients with agents. we are thinking of moving away from wsus and onto SCCM SUP. we have remote locations around the world. i want to put a test group together and try it out. A. how can i do this with each forest or domain having a GPO to direct to a WSUS server for updates. - this can be disturbed b. what steps should i take to ensure this test group can get updates from the SUP server and not the WSUS. I require to start small and work my way little by little up to the whole orgaization being patched this way. i plan to either decommission the old WSUS servers or strip WSUS off and use them as DP's. is this a good idea? should i just decommission them all at once and then bring up new DP's servers? we went a head and had someone come in and already setup the SUP point before me. i see now some clients are currently getting pointed to the WSUS server and some are pointed to the SUP server. how can this be fixed. i could turn off the SUP agent in the client agents and they should go back, correct? if i do this how can i test. i require a simple way of doing this, but i think this is going to be not easy. any help would be great.if i have made anything unclear please let me know.

here is the only log ==========[ ccmsetup started in process 6180 ]========== ccmsetup 11/29/2010 11:08:34 AM 10200 (0x27D8) Version: 4.0.6487.2000 ccmsetup 11/29/2010 11:08:34 AM 10200 (0x27D8) Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 11/29/2010 11:08:34 AM 10200 (0x27D8) Command line: ccmsetup.exe /mp:cpccm01.corp.dsg.local SMSSITECODE=DSG SMSMP=cpccm01.corp.dsg.local SMSSLP=cpccm01.corp.dsg.local CMALLOWSILENTREBOOT=0 FSP=cpccm01.corp.dsg.local resetkeyinformation=true ccmsetup 11/29/2010 11:08:34 AM 10200 (0x27D8) User credentials are not required to access installation files. ccmsetup will be executed in service-only mode. ccmsetup 11/29/2010 11:08:34 AM 10200 (0x27D8) Updated security on object C:\WINDOWS\system32\ccmsetup\. ccmsetup 11/29/2010 11:08:34 AM 10200 (0x27D8) Sending Fallback Status Point message, STATEID='100'. ccmsetup 11/29/2010 11:08:34 AM 10200 (0x27D8) sending with winhttp failed; 80072ee7 FSPStateMessage 11/29/2010 11:08:36 AM 10200 (0x27D8) sending with winhttp failed; 80072ee7 FSPStateMessage 11/29/2010 11:08:39 AM 10200 (0x27D8) Ccmsetup is not registered in the Run key ccmsetup 11/29/2010 11:08:39 AM 10200 (0x27D8) Successfully created the ccmsetup service ccmsetup 11/29/2010 11:08:39 AM 10200 (0x27D8) Failed to start the ccmsetup service (1053) ccmsetup 11/29/2010 11:08:39 AM 10200 (0x27D8) Sending Fallback Status Point message, STATEID='301'. ccmsetup 11/29/2010 11:08:39 AM 10200 (0x27D8) sending with winhttp failed; 80072ee7 FSPStateMessage 11/29/2010 11:08:41 AM 10200 (0x27D8) sending with winhttp failed; 80072ee7 FSPStateMessage 11/29/2010 11:08:43 AM 10200 (0x27D8) 8i can ping the SCCM server by name and fqdn as well. the domain this machine is in doesnt have the schema extended, but where the sccm server is the schema is extended. there is a network account set and a sccm client account defined with domain admins credentials supplied in the current domain where this machine is present.

i will delete all the logs and rerun the setup again and post the 2 logs.

here is the clientmsi log file to look at...not to sure what to look for. client.msi.log

I have some machines in which are both windows 2000 and 2003 on these machines i have tried to install the client and keep getting error 1603. i have tried uninstalling and reinstalling and still get no where. it is a VM as well if that matters. the error differs from machine to machine. i can start with one and move on to another. i have tried the uninstall register atl.dll file and doesnt work. this client machine, for which the setup log is attached has no problems with WMI and i can connect to it fine. any thoughts? the other machines i which i require help with are a bit more difficult as WMi i think is broke and need help on thise, but will deal with those machines after this one. ccmsetup.log

Issue is resolved. i have fixed it. here is how it was done. i noticed that the only user that had admin access was the NT Authority\System user. so i did some digging and found this tool called PSEXEC from http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx after getting downloaded and at a command prompt i got access denied still. did some more digging and found the correct syntax whish is rename the psexec.exe to psexec-setup.exe and then at a command prompt use psexec-setup.exe -s (for system account) -i ( for interactive) \\servername cmd (for command prompt) once there i got a cmd prompt for the system by using whoami and got nt authority\system. next I opened mmc and added the snap-in and went through the database connection wizard. gave myself the correct permissions and volia instant access. one word of advice ( needs to be done at the console no rdp sessions, no rdp session using the mstsc /admin ) it doesnt work. but i would like to say a big thanks to everyone who helped out. i really appreaciate it very much.

Sorry i cant find anything on this topic any where. if you know of anything please let me know.

I had a junior admin do some work and he accedently removed the admin accounts from the sccm console. luckly enough i have read only to a couple of accounts. my huge question is how do i get it back? i really need it, do the DBA's have to restore the database? please help....urgent!!

Hello: I have curently 1000 machines that i manage hardware and software inventory only...no wsus or pxe....YET. now, my boss has decided that he is going to construct a new AD Forest. he would than like to take the sccm clients from the current forest over to the new forest. after that is completed he than wants to pull the plug on the current SCCM Server and use only the new one in the new forest...question, is this possible or no? if it is, how simple can it be done? By GPO or something?

each product is installed in one group of servers and that group has nothing else installed. so product 1 has product 1, no product 2 or 3 or anything else thats all. than each product gets it own collection. so really the structure will look like: Product 1 Product 2 Product 3 all of these are seperate collections under Collections in sccm Product 4 Product 5 each of these have seperate collections and only 1 maintenance window which i would like to be 5 weeks...now the question how do i make a 5 week maintenance window on each one of the collections. the collections are not affected by any other maintenance window...no other links to collections are there, the servers are not in any other collections or maintenance windows except the all systems collections...no maintenance window.

ok let me see if i can explain it a bit better...maybe i am not clear enough in the sccm console under the colloections i want to make 5 seperate collections, product 1, product 2, product 3, product 4, product 5. now for each different product i would like to make a 5 week maintenance window so product 1 starts june 3 product 2 is june 10, product 3 is june 17, product 4 is june 24, product 5 is july 1. now product 1 is patched june 3 and in 5 weeks from then on july 8th it should come around to a maintenance window to allow patching and other things. product 2 would be july 15th....so on and so forth. i hope this i abit more clear of what i am asking to see if it is possible....now i figure that if i patch product 1 on june 3rd and set the maintenance window to be the effective date of june 8th, a week later, and then reoccur every 4 weeks does that not bring it to a total of 5 weeks? is there an easier way of doing this...if so please help.

Sorry it is not per windows product. it is per My Company's product we make. so if product 1 is on the first saturday of june, lets say, in 5 weeks which is 10th of July is the next time it would get patched. product 2 is the second saturday of june, then 5 weeks later on the 17th of July it gets patched again. i hope that explains it better. but each product would get its own collection for this reason.

I was wondering my company has 5 different products including infrastructure in which they would like to patch. they prefer to do 1 product every weekend, on Sunday. So I was wondering how I can set up a 5 week maintenance window for these products. The one thing I have found that might work is to patch on the Sunday and configure the maintenance window to start the next week and re-occur 4 weeks after that. I tried using the 5 weeks in the maintenance window and it wont allow me to use that amount of time. Does anyone have an idea?

It doesnt allow me to automatically set the wep key in the gpo if so i must be missing something. but i just need a way of doing a osd and having the wep key installed on the machine. is there a way to do this before the capture? if so, how do I do that i have tried and look for a simple way.

i have been trying for a couple of weeks now to try and deploy WEP keys to a windows 7 test machine. i have gone and tried to find some way of deploying them and thought i had it figured out by using a script. but either the script or something else is not working with each other. here is what i do for the script. netsh wlan export profile name=”CorpWIFI” ' It will make a file called Wireless Network Connection-CorpWIFI.xml and copy to the c drive netsh wlan add profile filename=”C:\Wireless Network Connection-CorpWIFI.xml” netsh wlan connect CorpWIFI after i do this it completes fine but it asks for the wep key. i have looked on various forums and i can not get this to work. any help would be great. i have tried on 3 different machines and all do the same thing.

How do I set up desired configuration management in order to get a compliance report that shows the amount of servers that are running local time as EST.