
Elioti
Established Members-
Posts
57 -
Joined
-
Last visited
Everything posted by Elioti
-
can't fix it can anyone help me out telling me which logs I can verify or other suggestions? thanks in advance I can't go further yesterday I checked my server ...more erros have been occured I will post some screenshots I need to know where it goes wrong ; any help would be appreciated(221 Views)??someone has to know ,isnt?
-
thanks I m quite sure the firewall of windows is disabled, maybe Have to check AVG is installed into that vista setup...and that could be the cause will keep posting of this eventually PEBKAC
-
no this is my problem the client doesnt appear into my vista client the vista pc is findable into collections " all systems" tried to deploy firefox into that client pc but the sccm client wont install ? which logs can I check logs on the client?C:\Windows\System32\CCM\Logs
-
can anyone help me further ..? I tried to deploy firefox as described but the test pc (client) doesnt receive the sccm client .. what can I do ? thanks for the info Wim
-
oops I guess I found the mistake of the SQL sysadmins I m logged in as administrator of Domain==>domain\Administrator but I gave the sql name and SDK server a different then the pc description! where can I change this or ....is thisn't the solution about the sql error?? thanks about extend the schema took the extad tool from the SCCM cd ,pasted into system 32 ran it and output.txt= Microsoft System Center Configuration Manager v4.00 (Build 6487) Copyright © 2005 Microsoft Corp. Successfully extended the Active Directory schema. Please refer to the SMS documentation for instructions on the manual configuration of access rights in active directory which may still need to be performed. (Although the AD schema has now be extended, AD must be configured to allow each SMS Site security rights to publish in each of their domains.)
-
Hello Guys, long time ago I started but for a whole of reasons I had to stop it, so now I have time to get into SCCM...I installed windows 2008 STANDARD version SQL 2005 Sp2 + visual studio update +sp3 added all the roles and features as described ..in the sccm guide Ran the prere... checker... 2warnings schema extensions and WSUS SDK on site server 3errors SQL server sysadmin right Domain membership Short file Name 8.3 support Site system what can I do about the errors ..still searching in the forum for the shema extension I tried with the elevated prompt extadsch.Exe Acces denied it says even that I added schema admins to the entreprise admin(secuirty tab) I m logged in as local administrator but checked en in also in that group,member of schema,entreprise,administrator,domain admins etc... don't know why ...? thanks for helpin me out in advance best regards
-
LOG[Failed to open to WMI namespace '\\.\root\ccm\Policy\Machine' (8007045b)]LOG]!><time="20:51:11.406+-60" date="11-04-2010" component="CcmExec" context="" type="3" thread="3416" file="wminamespace.cpp:231"> <![LOG[Could not connect to machine policy WMI namespace to get service settings.]LOG]!><time="20:51:11.406+-60" date="11-04-201
-
please help me out now my confirmgr wont connect to the db :s see screen
-
was checkin my confirmgr status "In the past 168 hours, SMS Client Configuration Manager (CCM) has made 8 unsuccessful attempts to install SMS on client "WINXPCLIENT". CCM will continue to attempt to install this client. Possible cause: The client is not accessible. Solution: Verify that the client is connected to the network and that the SMS Service account or (if specified) the SMS Client Remote Installation account have the required privileges, as specified in the SMS documentation." when I try to run a report get also this error HTTP Error 404.3 - Not Found The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map. I can surf on the inet (server+inet) will search further to solve this issues ! any help is welcome !
-
ok what can I do about this issue ? when I was setting up my sscm server reading part Step 2. Setting and configuring the site system roles. Open Active Directory Users and Computers and create two new Domain Users SMSadmin and SMSread. I have an issue by creating the 2 users The SMSAdmin account should have Full Administrative priveledges on the SCCM server. To do this you can add the SMSadmin account to the Local Administrators Group on the SCCM Server. I created them but the last point didnt succeeded(bold) hope I can get out cause I'm busy with sscm and I begin lovin' it!
-
sorry the file couldnt attached as I tried before!
-
atteched the sccm ccmsetup log (C:\WINDOWS\system32\ccmsetup)
-
oow yeah forgot to mentioned now it s a xpclient the Win7 client got a problem in AD !!! found the ccm.log Wmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e~ $$<SMS_CLIENT_CONFIG_MANAGER><Sun Oct 31 16:17:25.546 2010 W. Europe Standard Time><thread=4800 (0x12C0)> ---> Unable to connect to WMI ® on remote machine "WINXPCLIENT", error = 0x8004100e. $$<SMS_CLIENT_CONFIG_MANAGER><Sun Oct 31 16:17:25.546 2010 W. Europe Standard Time><thread=4800 (0x12C0)> ---> Creating \ VerifyingCopying exsistance of destination directory \\WINXPCLIENT\admin$\system32\ccmsetup.~ $$<SMS_CLIENT_CONFIG_MANAGER><Sun Oct 31 16:17:25.546 2010 W. Europe Standard Time><thread=4800 (0x12C0)> ---> Copying client files to \\WINXPCLIENT\admin$\system32\ccmsetup.~ $$<SMS_CLIENT_CONFIG_MANAGER><Sun Oct 31 16:17:25.562 2010 W. Europe Standard Time><thread=4800 (0x12C0)> ---> Updated service "ccmsetup" on machine "WINXPCLIENT". $$<SMS_CLIENT_CONFIG_MANAGER><Sun Oct 31 16:17:25.750 2010 W. Europe Standard Time><thread=4800 (0x12C0)> ---> Started service "ccmsetup" on machine "WINXPCLIENT". $$<SMS_CLIENT_CONFIG_MANAGER><Sun Oct 31 16:17:25.828 2010 W. Europe Standard Time><thread=4800 (0x12C0)> ---> Deleting SMS Client Install Lock File '\\WINXPCLIENT\admin$\SMSClientInstall.ZUS'~ $$<SMS_CLIENT_CONFIG_MANAGER><Sun Oct 31 16:17:25.828 2010 W. Europe Standard Time><thread=4800 (0x12C0)> ---> Completed request "FGRXMVMW", machine name "WINXPCLIENT". $$<SMS_CLIENT_CONFIG_MANAGER><Sun Oct 31 16:17:25.843 2010 W. Europe Standard Time><thread=4800 (0x12C0)> Deleted request "FGRXMVMW", machine name "WINXPCLIENT" $$<SMS_CLIENT_CONFIG_MANAGER><Sun Oct 31 16:17:25.843 2010 W. Europe Standard Time><thread=4800 (0x12C0)> <======End request: "FGRXMVMW", machine name: "WINXPCLIENT". $$<SMS_CLIENT_CONFIG_MANAGER><Sun Oct 31 16:17:25.843 2010 W. Europe Standard Time><thread=4800 (0x12C0)>
-
hi Peter, Client push installation Account :s:s is this the smsadmin and smsread that i created in ad ? @ the client I m logged in with the domain admin same as I m logged in @ the server so I know this isn't the way but just testin around so the account is also administrator on the W7 machine (client)
-
still working and did the whole guide follow through have an issue to create SMSread and SMSadmin ,can create them but the known 'errrors" The SMSAdmin account should have Full Administrative priveledges on the SCCM server. To do this you can add the SMSadmin account to the Local Administrators Group on the SCCM Server. To successfully install the Configuration Manager 2007 client, the Windows user account used must have Local Administrative rights on the destination computer. If the install fails with all accounts in the list then the installation will be attempted using the computer account from the Configuration Manager 2007 site server. If the user account does not have Local Administrative permissions on the destination computer then the Client will not install. so my client pc doesnt have (don't see it anywhere) sscm client not in control panel :s this reason above is the issue isnt? thanks for the help in here!
-
SOLVED THIS ISSUES
-
thanks for the quick réspons ok reinstalled SQL with SP2 issue solved next issue is when installing sccm SP2 the updates won"t dowwnload so something wrong with the inet settings on the server guess to reduce the security settings but this as user logged in can't be changed :s still searching
-
Hi , setting up sccm 2007 I have vmware an vmware client installed with server 2008 standard edition with sccm (en_system_center_configuration_manager_2007_with_service_pack_2_x86_dvd_447809.isoconfigmgr07sp2rtm_select_enu_6487) SQL 2005 standard with SQLServer2005SP3-KB955706-x86-ENU en_SQL_server_sp1_x86 followed the guide in this section schema admin ok <10-30-2010 02:18:25> Successfully extended the Active Directory schema. ok now the first obstacle when I run the prerequisite checker 'screen 1' I saw the known error explained in the guide topic but the link doesn't work anymore :s Either the user account running Configuration Manager Setup does not have sysadmin SQL Server role permissions on the SQL Server instance targeted for site database installation or the SQL Server instance could not be contacted to verify permissions. Setup cannot continue. screen 2 warnings! = info!
-
I have installed the sccm server which countered a lot of problems with criticals etc... anyway in one way or another it wasnt possible to deploy xp SP3 so we wants to deploy WIN7 x86 version so I installed SP2 on the sccm server in order to deploy win 7 entreprise edition. I need some Real support in here I have made some screens , but I know it isn't finished cause it gives errors and like you can notice in the screens the WDS WSUS etc isnt installed or scratched during the update(my opinion) I give the link so you can check the differents screens and hope you can help me further it's a deadline thanks in advance
-
will reinstall like you ^posted before.
-
wil post the images back later on but was cleaning my whole webspace!!
-
going bringing some screenshots to properly explain this problem the component status gives 2 warnings and 1 critical error. the 3 screens under gives you the first warning ,second and so on. this is the critical error =>
-
update= tried to open (on a client) http://SERVERNAME/sms_mp/.sms_aut?mpcert gives 500 - Internal server error. There is a problem with the resource you are looking for, and it cannot be displayed. webconfig!??? these folder is empty I guess we have removed teamfoundation and the folder is empty! web.config should be in this folder? dont tell me I have to reinstall the whole SCCM server :s should this help if I reinstall the iis or is this a different problem.
-
konetie thanks for your support tomorrow first step i will check the IIS
-
searching further for possibles causes :s I was reading this error warning: MP Control Manager detected DMP is not responding to HTTP requests. The http status code and text is 500, Internal Server Error. Possible cause: DMP encountered an error when connecting to SQL Server. Solution: Verify that the SQL server is properly configured to allow Device Management Point access. If using a standard SQL security account, verify that the SQL Server is configured to allow standard SQL Security; or configure the Device Management Point to use an NT integrated security account, with appropriate access. If using integrated security, verify the account used by the DMP to connect to the SQL server is a member of the SMS_SiteSystemToSQLConnection_<sitecode> group on the SQL server, that the account is not locked out, and that the account password is not expired. (In standard security, the default account is SMS_SQL_RX_<sitecode>.) Possible cause: The SQL server Service Principal Names (SPNs) are not registered correctly in Active Directory Solution: Ensure SQL server SPNs are correctly registered. Review Q829868. Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which SMS is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which SMS is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. Possible cause: The SMS ISAPI Application Identity does not have the requisite logon privileges. Solution: Verify that the account that the SMS ISAPI is configured to run under has not been denied batch logon rights through group policy. For more information, refer to Microsoft Knowledge Base article 838891.