I am trying to install the SCCM 2007, I built 2 servers:

ADSCCM (Active Directory usig Windows server 2008 R2)

SCCM2007 ( SQL 2008 + SCCM 2007 SP2)

Created 2 groups called:

SCCM-Admins

SQL-Admins

I also created 2 users called:

sccmadmin

sqladmin

I added “sccmadmin” to SCCM-Admins” group and I added “sqladmin” to ” SQL-Admins” group, then I added both groups to the “Domain Admins” group and “Administratros” group.

I installed SLQ 2008 on the SCCM2007 server; I logged in as Domain Administrator during the installation I used sccmadmin account for Server Configuration then for the Windows Athentication I used the two groups I created before, I follow this link:

http://www.petenetlive.com/KB/Article/0000297.htm#.UOJiym_nu6M

Once the SQL is installed then login to the SCCM2007 server as sccmadmin to install the SCCM2007 when I ran the prerequisite I got 2 errors:

• 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.
• 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.

One thing I don’t understand I know the SQL 2008 does not care about the domain admin account because both groups SCCM-Admins & SQL-Admins are member of Domain Admin group, having said that during the installation I specify both groups run the SQL server as administrator.

I disable the firewall.

I logged to MS SQL Studio and I checked both groups, they have have sysadmin permsion

It is very frustrating, if you come across this problem can you please share your experience?

Thanks in advance.

Hello,

we got new SAN space for our ConfigMgr 2012 R2 Server. So we have to move our ConfigMgr Partition (DriveLetter D:) to the new Partition (temporary E:, but will changed to D: after Migration)

my current plan:

1. Stop all relevant services for Configmgr (SMS Agent Host service. etc.)
2. Robocopy all data from D: to E:
3. Remove driveletter D: from old partition
4. Change driveletter E: to D: at new partition
   
5. Start all relevant Services

I guess all Shares of ConfigMgr (SMS_CAT, SMS_Site) get lose and i have to create them again? Is there anything else i have to care about?

Hello

I am facing a problem with SCCM2007, it was all working fine (client push, reporting back ....) but all of the sudden I noticed that in the sccm console it says, ASSIGNED YES, APPROVED N/A, CLIENT NO. I tried to install agent manually in the client computer but still the same issue. ..please help me to fix this issue...

Hi all,

Currently i have one SCCM server setup and it already has distribution point role installed. We have several branches with limited network bandwidth and file server for each of them.

My question is, is it possible to add more than one distribution point to one SCCM server and assign them to related branch? I am considering to set the file server on each branch as additional distribution point on the master "SCCM" server. How can i achieve this?

Thanks.

Has anybody tried to automate Configuration Manager 2007 SSRS Backup / Recovery process to a new hardware thru AfterBackup.bat?

Manual:- .
http://technet.microsoft.com/library/ms155814(SQL.100).aspx

Thanks and Regards, Mohd Zaid www.techforcast.com

Hi, i am using sccm 2007 sp1as a primary site, sql 2005 wit cu4, wsus 3.0, on same server 2008 sp2.   Few days ago i came to know that sccm console is not opening well so i checked the logs and found at sql database is showqing in suspact mode. So i used some sql alter commands that i have already used for same issues i faced in past. But that query only changed the mode to emergency. Than i googled alot to make the database online but got no result. Then i detached the database and attached it with old previous backuped database. After server restart sccm console is opening well even the reporting is also working well. There was issue with MP but reinstated MP again and now its also working fine with status code 200. Now the big issue is with the component status is not getting updated and showing critical. I have tried :-

Reseting count for errors.

MP and SUP reinstallation.

Checked sql and dcom permission as sccmadmin have all admin and sysadmin rights.

Given again permission on system management container.

Wsus reinstalled and synced properly with upstream server.

Hello..

Heres a short bref on the setup.

I run a windows Server 2008 R2 x64 Server with Hyper-V

On the Hyper-V part i run a virtual server setup (DC server, SCCM server, SQL server and so on..) and they all run Windows server 2008 x86 SP2 whit all updates. The AD is extended, the SCCM is 2007 SP2 R3 and the SQL server is 2008 SP3.

The thing is that i can't install the client software on the clients and the little dianostic tool say that my defuld site is stoped..

Is there any whay to fix this? i have tryed to start the site in IIS but it say that i can't do i becuse of some port problem.

Hi,

I'm hoping someone can help me with a primary site upgrade error from SCCM RTM to SP1.  Environment is 1 primary running 2003 SP2 x86 with remote SQL2005 SP2 x64.  I have not extended the schema so far.

The prereq fails with security mode error : Configuration Manager sites have only one security mode. That mode is equivalent to SMS 2003 advanced security mode. All SMS 2003 sites to be upgraded should be functioning in advanced security mode before beginning the upgrade process

I am not upgrading from SMS - this is a fresh install of SCCM on fresh OS

Also in the logs I see this:

Site XXX may not be running under advanced security mode. Either it is running under standard security mode or the security mode info cannot be obtained. Make sure the site is active and running under advanced security mode

- Is site security info recorded in the schema perhaps ??

So I tried an unattended SP1 install using setup /upgrade <my product key> & got this error:

Product Key XXXX-XXXXX-XXXXX-XXXXX-XXXXX can not be used on a Full Installation
> The setup command line option is not valid on this computer

Strange as I am upgrading from a Microsoft RTM cd install with my product code burnt in

Everything else looks fine, just warning on schema not extended, and I can see setup checking SQL etc

Cheers,

Ian

Client Pushes are working fine using the user account configured in the "Client Push Installation accounts" properties but it is my understanding that if you do not configure a user account or the user account you have configured doesn't have local admin rights on the client, the Client Configuration Manager (CCM) will attempt to use the Site Server's computer account to perfrom the install (Running Advanced Security in Mixed Mode - Schema Extended). This is confirmed by looking at the ccm.log site log. The ccm.log shows the CCM will first try using the user account and if that fails, will try using the site server's computer account (a.k.a machine account) to connect to the administrative share (admin$) on the client but it fails with the following error:

---> Attempting to connect to administrative share '\\xxxxxxx\admin$' using machine account.       SMS_CLIENT_CONFIG_MANAGER 
---> Failed to get token for current process (5)                                                                            SMS_CLIENT_CONFIG_MANAGER
---> ERROR: Failed to connect to the \\xxxxxxx\admin$ share using account 'Machine Account'       SMS_CLIENT_CONFIG_MANAGER 

Also, every 20 minutes (1200 seconds) a Account Cleanup Operation occurs in the ccm.log:

~ Doing Account Cleanup Operation ....                                                                                                                    SMS_CLIENT_CONFIG_MANAGER 
~ Processing domain XXXX                                                                                                                                     SMS_CLIENT_CONFIG_MANAGER 
~ Trying each entry in the SMS Client Remote Installation account list                                                                         SMS_CLIENT_CONFIG_MANAGER 
~ Attempting to connect to administrative share '\\\admin$' using account 'xxxx\xxxxxxx'                                            SMS_CLIENT_CONFIG_MANAGER 
~ WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account xxxx\xxxxxxx (000004b3)           SMS_CLIENT_CONFIG_MANAGER 
~ WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account xxxx\xxxxxxx (000004b3)                    SMS_CLIENT_CONFIG_MANAGER 
~ Attempting to connect to administrative share '\\\admin$' using machine account.                                                      SMS_CLIENT_CONFIG_MANAGER 
~ Failed to get token for current process (5)                                                                                                              SMS_CLIENT_CONFIG_MANAGER 
~ ERROR: Failed to connect to the \\\admin$ share using account 'Machine Account'                                                      SMS_CLIENT_CONFIG_MANAGER 
~ Failed to connect to Server. Error 5                                                                                                                        SMS_CLIENT_CONFIG_MANAGER 
~ Account Cleanup Operation Completed successfully.                                                                                                SMS_CLIENT_CONFIG_MANAGER 

• Both accounts (Site Server and Client Push User account) have local admin rights on the clients.
• Firewall settings have been properly configured...even turned off the firewall to make sure it wasn't a firewall issue (shotgun troubleshooting)
• On the Site server, opened up cmd.exe under the system account (psexec -s -i cmd.exe) and was able to map a drive to the admin$ on the clients 
• Checked NTLM Group Policy settings and DCOM security...all appear to be fine

Like I said earlier, the user account works fine but I have some departments that refuse to allow that user account to have local admins rights on their systems but will allow the Site Server's computer account. (Tighter security using computer account vs. user account.)

This query is regarding the purchase of Microsoft System Center 2012 and Its Dependencies.

This forum's link was provided by Microsoft Live Chat Support staff.

The query is:

Is there any official Document from Microsoft regarding the Warranties on the Following S/W products?

1. Microsoft System Center 2012 R2

2. Windows Server 2012 R2

3. SQL Server 2014

4. Windows CALs for the above.

If any, please provide the link as the Microsoft Authorized  Resellers have quoted "Warranty As Per OEM Terms", in their bids.

I get this error in my CCM.log after trying to install on a client server 2003 sp2.

---> Connected to administrative share on machine LCAPP22.lc100.net using account 'lcdom100\XXXXXX' SMS_CLIENT_CONFIG_MANAGER 11/26/2007 1:43:01 PM 7856 (0x1EB0)
---> Searching for SMSClientInstall.* under '\\LCAPP22.lc100.net\admin$\' SMS_CLIENT_CONFIG_MANAGER 11/26/2007 1:43:01 PM 7856 (0x1EB0)
CWmi::Connect(): ConnectServer(Namespace) failed. - 0x80070005 SMS_CLIENT_CONFIG_MANAGER 11/26/2007 1:43:01 PM 7856 (0x1EB0)
---> Unable to connect to WMI on remote machine"LCAPP22", error = 0x80070005. SMS_CLIENT_CONFIG_MANAGER 11/26/2007 1:43:01 PM 7856 (0x1EB0)
---> Deleting SMS Client Install Lock File '\\LCAPP22.lc100.net\admin$\SMSClientInstall.R01' SMS_CLIENT_CONFIG_MANAGER 11/26/2007 1:43:01 PM 7856 (0x1EB0)

Using Administrator WMI can able to connect and ccmsetup service able to start for client push method.

but using domain administrator account could not able to connect WMI and not able to start ccmsetup service.

Please Advise

Thanks in Advance

Hello,

- SCCM 2007 R3

I verified the boundaries.

I verified the Discovery Methods.

Everything looks okay.

When the SCCM Agent is deployed by GPO or from the SCCM Console I don't see anything on a lot of workstations.

8 machines on the same subnet, same OU, but only 2 received the SCCM Agent.

on the others I even do not see the CCMSETUP folder and no activity in the ccm.log...

Where to look now?

Thanks,

Dom

System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

We have a remote office with several PC’s that do not have the SCCM client.  Some systems are not being discovered by SCCM discovery and we will have a local IT contact install the SCCM client on these systems manually.  I have already read the TechNet article on manual installs, but it only relates to running manual setup over network from a SCCM site.

 A few questions:

 1. I may have them install client from the local site ‘\\siteserver\Microsoft Configuration Manager\Client\ccmsetup.exe’ over the network.  (This site is also a proxy MP.)  However, if they have difficulty doing this, what is the best method to install the client without connectivity back to the SCCM server?  Have them copy down the whole ‘Client Folder’ (containing folders i386, X64, etc) and have them double click on ccmsetup.exe from this folder on the local PC?                          

2.  Or would it work if they just copy down ccmsetup.exe file by its own and run this locally? Our AD Schema is extended so at some point these ‘blank’ SCCM clients will pick up their client config settings (MP, Cache, etc) correct?  Or must switches be specified (/MP:server /SITECODE: AAA, etc) when running ccmsetup.exe locally?

3.  Can they just copy down ‘ccmsetup.msi’ file and run this file by itself on the XP system?  

Hi,

We have two primary SCCM 2007 sites managing over 7K clients. for one of primary server performance issue, we want all clients to be managed by single primary site.

By moving boundaries from ABC to XYZ site, do you think that client will assign to XYZ site automatically? or we have to manually assign clients from ABC to XYZ site?

Note:

- Client push not enabled.                                                                                                                                                 - Active directory schema extended.

Thanks in advance....!

Hi,

I have search through the forum and Google extensively but I am not able to get any useful solution, I have around 100 machines in my environment and out of those only one of the windows 7 machine is having issues installing sccm client, I have tried installing manually but the same error appears. Any help would be highly appreciated.

MSI (s) (C8!DC) [10:48:46:241]: Closing MSIHANDLE (4977) of type 790531 for thread 7132
MSI (s) (C8!DC) [10:48:46:241]: Closing MSIHANDLE (4972) of type 790540 for thread 7132
MSI (s) (C8!DC) [10:48:46:241]: Creating MSIHANDLE (4978) of type 790531 for thread 7132
MSI (s) (C8!DC) [10:48:46:242]: Creating MSIHANDLE (4979) of type 790531 for thread 7132
Action start 10:48:46: CcmSetObjectSecurityInit.
MSI (s) (C8!DC) [10:48:46:242]: Closing MSIHANDLE (4979) of type 790531 for thread 7132
[10:48:46] @@ERR:25001
Error 25001. Setup failed due to unexpected circumstances
The error code is 80004005
MSI (s) (C8!DC) [10:48:46:243]: Product: Configuration Manager Client -- Error 25001. Setup failed due to unexpected circumstances
The error code is 80004005

MSI (s) (C8!DC) [10:48:46:244]: Closing MSIHANDLE (4971) of type 790531 for thread 7132
MSI (s) (C8!DC) [10:48:46:244]: Closing MSIHANDLE (4970) of type 790540 for thread 7132
MSI (s) (C8!DC) [10:48:46:244]: Closing MSIHANDLE (4978) of type 790531 for thread 7132
MSI (s) (C8!DC) [10:48:46:244]: Closing MSIHANDLE (4969) of type 790541 for thread 7132
MSI (s) (C8:20) [10:48:46:245]: Closing MSIHANDLE (4968) of type 790542 for thread 6432
CustomAction CcmSetObjectSecurityInit returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (C8:20) [10:48:46:247]: Machine policy value 'DisableRollback' is 0
MSI (s) (C8:20) [10:48:46:247]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
Action ended 10:48:46: CcmSetObjectSecurityInit. Return value 3.
MSI (s) (C8:20) [10:48:46:247]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (C8:20) [10:48:46:247]: No System Restore sequence number for this installation.
MSI (s) (C8:20) [10:48:46:247]: Unlocking Server
Action ended 10:48:46: INSTALL. Return value 3.
Property(S): UpgradeCode = {252DA259-82CA-4177-B8D0-49C78937BA3E}
Property(S): SourceDir = C:\Windows\ccmsetup\{4CD82FBB-0AFC-4864-A089-15364DF5F14B}\
Property(S): TARGETDIR = C:\Windows\SysWOW64\CCM\
Property(S): ALLUSERS = 1
Property(S): ErrorDialog = ErrorDialog
Property(S): ProductName = Configuration Manager Client
Property(S): ProductCode = {2609EDF1-34C4-4B03-B634-55F3B3BC4931}
Property(S): PackageCode = {4CD82FBB-0AFC-4864-A089-15364DF5F14B}
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 4.00.6487.2000
Property(S): ProductLanguage = 1033
Property(S): SystemFolder = C:\Windows\SysWOW64\
Property(S): Redist.51D569E3_8A28_11D2_B962_006097C4DE24 = C:\Windows\SysWOW64\

Hi,

We migrated clients from SCCM 2007 to SCCM 2012.
We need to speed up the process of deleting inactive clients (not many should be there).

The link below, tells us that the "delete inactive client discovery data" task can do this job but only does it every 90 days.
http://technet.microsoft.com/en-us/library/bb693646.aspx

Can we set this schedule to delete discovery data older then f.e. 1 week and run it safely? Inactive clients that  would be deleted erroneously would reconnect without any issue(?)

Pls advise.
J.

Jan Hoedt