Quantcast
Viewing all 443 articles
Browse latest View live

Unable to download MS updates during update list creation

Hi

I have SCCM 2007 SP2 (version  4.00.6487.2000) , when I try to create new Update List I receive the following error:

You do not have security rights to perform this operation.

These are my steps:

-select the MS updates and created new update list

-check option "download the files associate with the selected software updates"

-create new deployment package and set Name and Package source and check option" enable binary differencial replication" . (before I created a new share for the Package Source with correct rights).

-select the distribution point (it's the configuration manager).

-select "download software from the internet"

When I confirm the operation I receive this error:

You do not have security rights to perform this operation.

Have you any idea?

I also verified that when I select the MS update and right click, I have only the option "update list" and not the options "deploy software updates" and "download software updates"

thanks

Chris


Application/Program/Package Parameters?

I attempted in searching for this answer in a couple of the forums and the all famous troubleshooting website "Google", however I don't see a best method of accomplishing what I'm after. I'm currently on a project implementing SCCM 2012 (RTM, we'll be upgrading the servers soon once everything is configured district wide.) for a school district. However, each school uses the same program that can be installed by .MSI, but they all have a different install parameter to be used when issuing the msiexec /i command.

This is a question based towards more configuring an Application, Package, or Program for distribution that has msiexec parameters that need to change by the slightest per subnet/site. What is the best way to configure this .MSI deployment to minimize excessive device collections or 40+ different applications of the same .MSI with different parameters?

Changing a Boundary in SCCM 2007

I have a live SCCM 2007 environment, and I need to change the existing boundaries so as to accommodate a SCCM 2012 environment that we are introducing (and will eventually migrate to). The SCCM 2007 boundaries are all ‘IP address range’. So my question is as follows: if I delete an existing ‘IP address range’ boundary and create a new ‘IP address range’ boundary (all in SCCM 2007), what will the impact be on the SCCM 2007 Clients that were included in the old boundary, and now find themselves included in the new boundary? I assume that the next time to SCCM Client restarts, it will be assigned to the new boundary, and all is good. But if anyone has any direct experience of this scenario, I'd be interested to hear from you.

Thanks in advance for any advice, Rob

Can't Push Advanced Client

I've got a computer that's is driving me nuts!

This computer is at one of my secondary sites.   There are other computers at this site, and they're all working, but I can't get the Advanced Client installed on this one.

The computers appears in my All Systems collection.  It has the site code for my remote site.  If I try to install the client by right-clicking on the computer and selecting Install Client, I don't see any evidence that anything ever happens.  I don't ever see a .CCR file appear on the remote site server, I don't see anything in the CCM.log on the remote server, and I never see a CCMSetup or CCM file appear under sysWOW64 (I even checked System32 for good measure).

If I manually create a .CCR file and place in the ccr.box folder on the remote site server and watch the CCM.log file, I can see the .CCR get processed, but it reports "Mobile client on the target machine has the same version, and 'forced' flag is not turned on."  What might be present on this computer that would make SCCM think that the Advanced Client is installed on this computer.

I checked DNS and DHCP just to make sure this computer was the only one associated with its known IP address, but everything looks just like it should.

Site boundaries?  I've checked them, but I don't see anything wrong.  I've verified that this computers has an IP address within the AD site for that remote location and that the AD Site is the boundary for my SCCM Site.

SCCM Problem, Failed to send registration request


Hello,

I´m using the System Center Configuration Manager 2007.

In the ClientIDManagerStartup.log there is every time the same Error like:

 

Code Snippet

<![LOG[RegTask: Failed to send registration request. Error: 0x8000000a]LOG]!><time="06:47:17.531+420" date="07-25-2008" component="ClientIDManagerStartup" context="" type="3" thread="3308" file="regtask.cpp:1314">

<![LOG[RegTask: Client is not registered. Sending registration request...]LOG]!><time="08:55:17.531+420" date="07-25-2008" component="ClientIDManagerStartup" context="" type="1" thread="3308" file="regtask.cpp:1434">

<![LOG[RegTask: Failed to send registration request message. Error: 0x8000000a]LOG]!><time="08:55:17.546+420" date="07-25-2008" component="ClientIDManagerStartup" context="" type="3" thread="3308" file="regtask.cpp:1139">

<![LOG[RegTask: Failed to send registration request. Error: 0x8000000a]LOG]!><time="08:55:17.546+420" date="07-25-2008" component="ClientIDManagerStartup" context="" type="3" thread="3308" file="regtask.cpp:1314">

 

Pleas help me to get this error away, I don’t know what I have do to.

Thanks!

 

German:

Hallo,

Ich verwende den System Center Configuration Manager 2007.

In der Logdatei: ClientIDManagerStartup.log kommt immer der gleiche Fehler:

 

Code Snippet

<![LOG[RegTask: Failed to send registration request. Error: 0x8000000a]LOG]!><time="08:55:17.546+420" date="07-25-2008" component="ClientIDManagerStartup" context="" type="3" thread="3308" file="regtask.cpp:1314">

<![LOG[RegTask: Failed to send registration request. Error: 0x8000000a]LOG]!><time="06:47:17.531+420" date="07-25-2008" component="ClientIDManagerStartup" context="" type="3" thread="3308" file="regtask.cpp:1314">

<![LOG[RegTask: Client is not registered. Sending registration request...]LOG]!><time="08:55:17.531+420" date="07-25-2008" component="ClientIDManagerStartup" context="" type="1" thread="3308" file="regtask.cpp:1434">

<![LOG[RegTask: Failed to send registration request message. Error: 0x8000000a]LOG]!><time="08:55:17.546+420" date="07-25-2008" component="ClientIDManagerStartup" context="" type="3" thread="3308" file="regtask.cpp:1139">

 

Vielleicht habt ihr ja eine Ahnung wie dieser Fehler hervorgerufen wird und wie ich ihn wegbekommen kann. Danke für eure Hilfe.

Mit freundlichen Grüßen,

Argre

Powershell Script not creating shortcut to desktop after SCCM 2007 deployment?

I am currently in the process of deploying Windows 7 to a variety of PCs (Very new to powershell). The deployment its self is successful, however throughout the task sequence there is a specific step in which a shortcut must be created. After the deployment is complete there is no error or issue to say that the script had not been successful yet, it clearly has not worked. The shortcut is located on a server, but the step within the task sequence is run with the network administrator account, so I doubt it is a permission issue. If you run the script within PowerShell once Windows is installed it works correctly creating the shortcut to the application. If anyone has had a similar experience or any information which may help then I'd appreciate your input.

This is the command line sequence that is used within the task sequence:

powershell.exe -ExecutionPolicy Bypass -NoLogo -NonInteractive -NoProfile -WindowStyle Hidden -File .\AppShortcut.ps1

This is the actual powershell script.

$AppLocation = "\PROGRAM\Testprogram\TestApp\App.exe"

$WshShell = New-Object -ComObject WScript.Shell

$desktop = $wshShell.SpecialFolders.Item("AllUsersDesktop")

$Shortcut = $WshShell.CreateShortcut($desktop + "\App.lnk")

$Shortcut.TargetPath = $AppLocation

$Shortcut.IconLocation = "\PROGRAM\Testprogram\TestApp\App.exe"

$Shortcut.WorkingDirectory ="\PROGRAM\Testprogram\TestApp\"

$Shortcut.Save()

How manually remove a DP in SCCM 2007 ?

Hello,

we had a disaster and our old SCCM 2007 site server is dead.

We already have a SCCM 2012 site server up and running and a old SCCM 2007 distribution point still up.

we need to convert the old DP to a 2012 DP.

How can i manually remove the DP from SCCM 2007 without an access to the console, site server, bd, etc...?

On the DP, Can I just remove all the share and permission?

thanks

Prevent SCCM Client Installation on the target computers

I need a sure-fire way to prevent manual, automated, deployment, or push SCCM Client installs from specific computers (they are medical, and will violate FDA regulations if non-approved software is installed on them).  I'm aware of the Registry entry on the Site Server, but, am looking for something on the target computer side (RegHack, phoney file/folder, etc.).  Discovery of the computers, but inability to install the client is OK (we'll be removing them from the Discovery LDAP queries as needed).

Our SCCM Hierarchy is in one Domain, and the clients all in other Domains, so, I could look at excluding the client install account, but, that won't stop a manual or automated install.

Thanks.


SCCM 2007 R3 New DP , how to add to all existing packages

Hi

Is there a script which allows an SCCM 2007 R3 DP to be automatically added as a DP for all existing packages? I know this is easily done in 2012 with Powershell support or DP Groups, but was wondering how to automatically add a DP to all existing packages in SCCM 2007 R3

Any help greatly appreciated!

Thanks

Max

Link 2013 automatic activation

I am deploying link 2013 using sccm 2007, however it's not automatically activating for me. Below is the xml code i'm using.

I have included the command to do this but i still get prompted to activate after install. There is no issues with internet access.

Any help would be greatly appreciated.:)

  
 <Setting Id="SETUP_REBOOT" Value="Never" />
 <Setting Id="AUTO_ACTIVATE" Value="1" />
 
 

SCCM side by side upgrade

Hi!

We want to get a fresh start with SCCM, and not migrate data from our existing SMS servers over to SCCM.
In other words we want to have a SMS infrastructure and a SCCM infrastructure besides each other in the same AD domain, and move clients over to the new SCCM servers.

My plan is to take one site at a time and remove site boundaries from SMS, wait for replication and then recreate the site boundaries in SCCM. Then install SCCM client on the computers in that site.

We have tried this in our lab, but but have experienced SMS clients being automatically reassigned to the new SCCM site before we have changed the site boundaries!

How do I keep the two separate, and avoid client computers to being reassigned withour our control?



Regards,

Marius
Marius

Easy one! Client install directory permissions?

Could someone kindly share with me the default directory permissions for the ...Program Files\Microsoft Configuration Manager\Client folder on a SCCM 2012 primary server installation?

I inadvertently modified them thinking I was working on the copied version of that folder and need to reset them back.  Would prefer not to do the site reset option if at all possible.

Thanks!

Warranty Information for Microsoft System Center 2012 and Its Dependencies

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.

Thanks & Regards

Unable to connect to WMI on remote machine

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)

No CCMSETUP folder is created on the client machine, what should I be looking at next?

Client WMI Connecting Issue

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


SCCM Agent 2007 Push not doing anything!!!

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

Setup SCCM client manually question

 

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?  

SCCM client re-assign

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

SCCM Client on Windows 7 CcmSetObjectSecurityInit

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\

 

SCCM 2007: delete Inactive Client Discovery Data?

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

Viewing all 443 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>