hhancock
-
Posts
80 -
Joined
-
Last visited
Posts posted by hhancock
-
-
Hmm, the computer is showing in the log now and is showing in the All Systems device collection, however it's showing as inactive. I've since removed the device from the database and running another full discovery.
-
Make sure that it;s within the OU's that are configured in the discovery. For more information check the adsysdis.log file.
It's in the OU. My WDS server adds the computer to the domain and moves it to the proper OU. I've confirmed that the computer is in the correct OU.
-
It will also turn critical with a lot of warnings. What are all the warnings about?
It's actually now moved from Critical to Warning. The warnings appear to be certificate related.
MP has rejected a message from GUID:D3B6AE2C-D88F-49DB-A3C5-D5322CB7A2A0 because the signature could not be validated. If this is a valid client, it will attempt to re-register automatically so its signature can be correctly validated.
-
I am not 100% sure what's going on but if a computer is currently in AD and I use WDS to reinstall the image the computer name stays the same. This is not what I want at all. Usually, the computer is being reimaged and given to a new employee and we are using the USERNAMELT00 standard. Is there anyway to force WDS to create a new computer name every time I PXE boot? For the record, I do have the Client Naming Policy set to %61Username%02# in WDS. Any help would be greatly appreciated.
-
I have a device that's been in Active Directory for about two weeks but doesn't show in SCCM. Other devices more recently added to AD have been discovered and have successfully installed the SCCM client. How can I troubleshoot a single device?
I am using Active Directory System Discovery and have run a full discovery with no luck.
-
I recently noticed that the SMS_MP_CONTROL_MANAGER component is in a critical state. With that said, I don't see any errors when checking the messages, only warnings. What can I do to get this component back into an OK status?
-
I can't seem to get the WDSClientUnattend.xml file to work properly. I am trying to deploy a Windows 8.1 image. I've create a unattend answer file with Windows System Image Manager. The answer file validates. I've added this answer file to the WDS server properties client tab under the proper architecture (x64).
I am still prompted to input locale and credentials even though my answer file has this information already in it. On the client, the setupact.log file says, "There is no unattend file available on the server." I am confused because I see the file and I am able to browse to it from another computer on the network. I've created another post on TechNet.
<?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="windowsPE"> <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <WindowsDeploymentServices> <Login> <Credentials> <Domain>DOMAIN</Domain> <Password>PASSWORD</Password> <Username>USERNAME@DOMAIN</Username> </Credentials> </Login> </WindowsDeploymentServices> </component> </settings> <cpi:offlineImage cpi:source="wim:c:/sources/install.wim#Windows 8.1 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>Any guidance would be greatly appreciated.
-
I ended up having to do a wipe and reformat on this Windows 8.1 laptop. Not 100% sure what the issue was, but I guess WMI, even though it was a relatively new build. After re-installation of the O/S, the Software Center works.
Possible. I feel like I've seen a message about a corrupted WMI in the log before. By chance did you ever try to repair WMI? From my understanding, you can rebuild WMI on the client machine.
-
From my understanding, no. I don't use the Application Catalog heavily, but I believe that an administrator would need to login to the SCCM console and specifically look for any new software requests.
I'm told that there are 3rd-party addons, that will make this whole request/approval process smoother. I don't know the specific names of those add-ons, but someone else that uses this piece of the product could probably tell us some options.
Thanks. I don't really want to install Exchange in my lab environment but I guess it couldn't hurt. I'll look into 3rd-party addons as well. We are just trying to find a smoother way for users to request software and have it approved. Ideally, we'd like our HR department, or at least a representative from this department to approve requested software based on our MSDN subscription number. We find that the process of tracking who has what license to be rather cumbersome (in the MPN and MSDN sites).
I found a great article about using System Center Orchestrator and creating an ASP.NET application to do pretty much exactly what I want. I am going to try this out. Thanks again for the information.
-
When a user request software from the Application Catalog that must be approved, does an e-mail get sent out to the approver and or Administrators?
-
Ok so I've copied the Client folder to my server that I want to install config manager on. Ran it and checked the ccmsetup log. There has to be a simple solution as to why this is happening.
Based on this information, it appears that it's having issues finding the distribution point. Have you installed a distribution point on the server where you copied the client files to?
-
Yes, App Catalog is configured and works on all machines, except for this particular Windows 8.1 client. Part of the reason I'd really like to figure this out, is that I'm in the beginning stages of my SCCM 2012 deployment, and I'm not sure if this same error will crop up on additional machines. But if it does, I'd like to be able to resolve it (without a wipe and reformat.)
I've tested on Windows 8.1 and it works for me. Have you tried reinstalling the client?
-
Thanks for the tip, Peter. I've attached the SCClient_device@user.log. I don't want to attach the entire CCMSDKProvider.log, because it's got sensitive info, but here are a couple lines from that log file that look problematic:
Failed to get method for DeviceId. Return code: 0x80041002
Retreiving Application Catalog URL from Client Agent Config
Making call to get portalUrl from MP.
Failed to get method for retreiving Application Catalog URL. Return code: 0x80041002
Have you setup the Application Catalog in the Client Settings?
Administration > Client Settings > Default Client Settings
In the Computer Agent section, make sure a Default Application Catalog website point has been set.
-
Hi,
Have the devices the Configuration Manager 2012 client installed on them? If so the heartbeat that the client sends will also re-register the client back again regardless of the discovery settings. If you check properties of the client you are able to see what discovery method added the client and when, that way you can verify that you delete was succesful and what process is adding it back.
Regards,
Jorgen
Ah, that's what I was afraid of! So now, I will try to manually remove the SCCM client from the device, remove the device from the SCCM console/database and try again. Do I need to kick off any Site Maintenance tasks?
-
This is a known issue. Modifying the roles of an existing distribution point will reset the certificate settings of the distribution point. So - If you have a DP all set up and later decide to add / remove a role, you will need to reconfigure the certificate settings - import the cert. We broke this countless times before opening a ticket with Microsoft to have them tell us this.
Aaron, ours seemed to happen once we upgraded to R2. It's hard to pin down an exact time as we rarely use Configuration Manager and I don't really want to go that far back in the logs
Regardless, the issue is resolved.
-
well have you tried to gollow the advice in the description of each of the Message ID's above ?
Yes, as the Message ID's that are listed weren't really the problem. The real problem was that it couldn't contact the MP over HTTP. I've since resolved that issue by reissuing the web server certificate.
-
Hmm. Would there be any reason why devices are still showing up in my database if all discovery methods are disabled?
It seems that when I run select * from v_R_System it continues to grow...
I removed a computer using your method. I created a new Device Collection called Decommissioned. I then added a computer via a direct rule (Name). I then removed the device collection and selected to remove all devices in the collection from the database. Within 5 minutes, the device is showing back in the Configuration Manager console and the database. What gives?
Why does the device continue to show up even though I've removed it from the database and have turned all Discovery Methods off?
-
Correct. Although, if you're discovery method is say - Active Directory, and these stale objects that you remove from SCCM also exist in AD, they will import themselves right back into SCCM. We're actually in the process of this same thing here. We need to isolate the PCs that exist in AD that are no longer in use, have been recycled or stored, and / or trashed... and remove them from AD. At this point, removing them from SCCM will prevent them from being discovered again.
Thanks for this information. I have a script that moves the stale objects to another container in AD (which isn't being discovered in SCCM). Therefore, any stale objects should be not be added back to SCCM. I am in the process of removing all discovered devices from the SCCM database so it will be easier for me to understand how best to setup the hierarchy.
Again, thank you for the information as it's been a great help in understanding what I can do.
-
Create a collection using some criterion of machines that you'd like to delete. Let the collection build for a bit (depending on how large your database is). Once it's done - delete the collection. On the deletion confirmation box there will be a check box at the bottom that says "Delete Objects from Database"
This will ensure that the object is not just removed from the collection, but also the SCCM database as well.
Hope this helps
So, when I enable another discovery, said computers should be added back to the database, correct?
-
Hello,
I am in the process of reconfiguring our hierarchy and was wondering what the proper way to remove devices was. Currently, I have all the discovery methods disabled so that I can update the hierarchy. I've manually removed the devices from the Configuration Manager console and I don't get any errors, however, after a refresh most of the devices are still showing. Is there anyway to remove these devices from the database in order to reconfigure my hierarchy?
It's been a while since we've last used Configuration Manager so there are a lot of stale objects. I am hoping to clean everything up and really start utilizing this product in our organization.
Thanks in advance!
-
HHancock,
Here is a post on this topic:
As Peter suggests, your machine may not be using the correct certificate when browsing to the url, but that doesn't necessarily indicate that there's a problem. From that link above, "if you're seeing 'Call to HttpSendRequestSync succeeded for port 443 with status code 200, text: OK' in your mpcontrol.log as per my screenshot above, that's a good sign the MP is functioning correctly."
So, check out your mpcontrol.log, and see what you've got.
Ok, great. The mpcontrol.log does say that it succeeded. The Management Point is showing as OK and all of my clients are showing Active.
Thank you for your help!
-
Sorry to bring this really old topic back up. When I upgraded to System Center 2012 R2 Configuration Manager I started to see this issue. It appears that the certificate had expired. I've reissued the certificate and the Management Point now shows that everything is OK. However, when I try to navigate to the SMS_MP/.sms_aut?mplist URL I still receive a 403.7 error. I am not really sure what's going on. When I issued the certificate, I used the DNS name of myserver.domain.com. Any suggestions would be greatly appreciated.
-
Hello,
I've recently uninstalled the Management Point role on my primary site (only site). After reinstalling the Management Point role, it appears that the MP is stuck in a critical state. Since the reinstallation, I only see two errors (as shown in my screenshot):
Is there anyway to fix this? I've rebooted several times and haven't received these errors since but the MP remains "critical." Can I clear these events? I've tried resetting the count and refreshing the role but it still shows critical. All components have a status of OK.
-
It appears that the component has fixed itself.
Device Not Discovered
in Configuration Manager 2012
Posted
Removing the device from the database and performing a full discovery seemed to have worked. The device was rediscovered fine and the client was installed. The only thing now is to figure out why it's not showing up in the correct device collection.
I have device collections based on an OU called Workstations within another OU for each geography. For example, ATL > Workstations, BHM > Workstations, etc.
I think that it might not be showing up in the device collection because the schedule was set to run once every 7 days. I've since changed the rule for the device collection to once per hour. We'll see if it shows up. The device does show up correctly in the All Systems collection and is showing in the correct Active Directory Site.