We're running a chain of updates and installs via a Task Sequence, SCCM 2012 R2 and a mix of 7 and 10 labs. Some of the stations reported success in one deployment I made, others are reporting success in a deployment my coworker made (we were both testing at the same time and didn't communicate well enough).
While the machines have been removed from the deployment, Deployment Status still reports them in one deployment or the other. We'd like to remove the stations that Errored in one group, as they're reporting as Success in the other.
Is there any way to remove records from a Deployment Status for a collection in Monitoring?
I've been unsuccessful in my searches, won't be surprised if the answer is no, and sorry if this is a duplicate, I searched before asking.
It is possible to clear out status messages from sccm for a given period but not for specific systems that i know of. SCCM probably saves these in the database, You could try to delete them from there.
Related
I setup GoCD on an Ubuntu box and followed the instructions to create additional agents on that host.
The agents tab shows six agents, all enabled, all idle. One has the resource 'data' because I want to make sure some checked out artifacts go in a consistent place. The remaining five agents show "none specified" for resources or environments.
The Admin/environments page shows "no environments have been setup".
I've configured YAML descriptions of the jobs to be pulled from a repo. That works.
If I navigate through the "Config Repositories" pages and inspect the builds, there are no Resource listed on the job settings page.
And yet the pipelines are all just stuck "Waiting for an agent". Descriptions of this problem seem to imply that it's only caused by resources or agents, but I don't believe that's the case here.
Since I'd gone to the trouble of setting up "pipelines as code", I decided it would be easy enough to just start over (if at first you don't succeed, power cycle the device). I uninstalled the server and the agent, sorted out how to remove all the additional agents, and reinstalled everything.
Now it seems to be working.
My best guess is that somewhere in the server or agent, one of my various experiments with using resources had caused something to become confused.
It does not inspire confidence. :-(
Has anyone else encountered this problem:
Every month I apply windows updates to servers using SCCM Software Update Groups. Some servers are considered lower priority so I push the updates as required to the server and expect the updates to install and the server to reboot if necessary during its assigned maintenance window only to find out that the some of the updates are failing. With experience, I have found this is because the system is waiting for a reboot. I would expect that SCCM would know that there is a pending reboot and reboot the server during the maintenance window to finish applying the updates but it does not. It seems as though these are "pending reboots" that SCCM cannot detect.
As a result, this requires manual intervention each month on a dozen or more servers that have to be manually rebooted in the middle of the night so as to not interrupt production.
One of the biggest culprits to this issue is the monthly Malicious Software Removal Tool. It always seems to fail to apply then works after a reboot.
The Computer Restart related setting can be configured in the "Client Setting" node on your console. No matter if you determine to use the Default client setting or the custom client settings, you should make sure that that the value for the restart temporary notification interval and the value for the final countdown interval are shorter in duration than the shortest maintenance window that is applied to the computer (the default values are 90 and 15 mins). This is important for the deployments which require a reboot completed on your clients.
Additionally, you can examine the logs on the client-side as below:
Update deployments related logs: UpdatesDeployment.log, WindowsUpdate.log
Reboot & Maintenance related logs:RebootCoordinator.log,ServiceWindowManager.log
More details about how to track the Update deployment process in ConfigMgr can be found here.
My company is using clearcase on a linux server and the development environment under linux and windows 7.
The windows 7 machines are for snapshot only.
the problem we have is windows only.
For each clearcase command under windows, there is a lot of latency.
We noticed the process lsass.exe when we do ressource monitor/analyze wait chain of cleartool process.
The wait of cleartool on lsass cuase a latency going from 50 sec to 1 minute
The problem does not occur for all users and not all the time.
when the problem does not occur the cleartool process has no process on analyze wait chain.
We have clearcase 8 set on the server and clients with version 7 or 8 .
We are pretty sure it is not a clearcase problem.
I would like some information about lsass and see what could cause the wait on lsass.exe
lsass is the Local Security Authority Subsystem Service, is a process in Microsoft Windows operating systems that is responsible for enforcing the security policy on the system.
I have seen issues in the pass when an Anti-Virus was analyzing ClearCase views.
Try and deactivate as many process/service as possible in order to see if cleartool commands still experience this kind of latency.
ClearCase makes a LOT of calls to your domain controller(s). I have seen some "interesting" performance issues if the communication is sporadically or completely interrupted.
Can you explain where all the major players are in relation to one another? Including, but not limited to:
Windows domains. If there are multiple Windows domains, are they all AD domains in the same forest?
Domain controllers.
Clients.
VOB/View servers.
License servers? Type of licenses served (Classic Atria/Classic Flexnet/Tokens)
Are there multiple license servers in use? (if using FlexNet/Tokens)
A key heads-up is that there were some issues a couple of years back with the permissions on ...\ClearCase\var\cache on Windows. It could cause some pretty serious performance issues if users don't have the rights to create files and write to them here.
You may also want to take a network trace of one of these updates. If you see anything that flat doesn't belong (NetBIOS name broadcasts for your DOMAIN name would be one, as this is a last resort to get a DC address), you may need to do some investigation...
We're running TFS 2010 on a dedicated machine. The SQL db is also running on the same machine so there is no external LAN/WAN access there.
When we check in/out or get anything from TFS - the initial connection and any connections after some inactivity from VS is extremely slow, sometimes up to 1 or 2 minutes. Once it does whatever it has to do, things start run fast and move along with no problems whatsoever.
What/where should i check to find this bottleneck, or whatever it is that's turning off after inactivity ?
I think that it is similar to SQL Server Reporting services. When it is inactive for some time (20 min?) the worker process fall asleep and wake up time is rather long.
SSRS 2008 - Long delay after a period if inactivity, How to Speed up MS SQL Server Reporting Services SSRS on First Run. There should be similar setting for TFS webservices.
I suspect it is the traditional ASP.NET wakeup pipeline that you are running into. If you want to try out setting a scheduled task that runs PingTFS.exe then it will keep the site loaded so that you don't see this initial hit each time the TFS web services have cooled down.
You can find PingTFS.exe available from Neno Loje here: https://msmvps.com/blogs/vstsblog/archive/2011/03/02/how-to-ping-tfs-to-see-if-it-s-up-and-running.aspx
If that doesn't help, then it's likely the hardware in the environment. You definitely don't want to have too few of resources for your TFS environment. Let us know if the first suggestion doesn't work out.
Recently our Development user group (Windows) has started showing with a Red Cross in Team Explorer and we cannot expand it anymore.
I have tried removing and re-adding the group but to no avail.
Does anyone know why it would display like this?
We are using TFS 2010 with VS2010 SP1 and August's Power Toys.!
BTW, "Technical Testing Team" is another Windows Domain User Group, just like Development and that works OK.
In general, the red crosses on particular services are caused either by that service being unavailable or by permissions issues...
Are you still able to perform actions that require admin permissions? Does this apply to a single project or all?
How are you defining your developers? A windows domain group? If so, is the TFS server able to see the DC?
I'd suggest you try installing Team Explorer on the TFS server and running it when logged on as yourself - see if you have the same problem. If not, it may be network or firewall problems between your dev machine and the server. At least it would narrow the problem down.
Edit 1:
Do reports work properly? (Specifically, do the graphs show up in reports)?
What auth are you using? Kerberos?
What account is TFS running as? What permissions (if any) does that account have on the network?
Can you see the security information you'd expect in the TFS_Configuration database? (Try tbl_SecurityAccessControlEntry) [Usual "Change nothing, do it at your own risk" disclaimer]
Edit 2:
As per the install docs, the TFS service should be running under its own account (IIRC they suggest Domain\TFS.Service). Check the permissions on the windows services on the TFS Server and see who they're running as. Makes sure the permissions for that user are correct as per the installation instructions
NTLM can cause problems as it doesn't allow credentials to be delegated/relayed the way Kerberos does (and has some picky setup requirements) - but that's obviously not why it's broken all of a sudden (and that usually manifests as graphs not displaying in reports).
WRT: the SecurityAccessControlEntry table, I was more interested in making sure there were entries and that it could be read properly than the contents.
I assume you've tried deleting/recreating groups - If not, give it a shot (deleting the domain group may be an issue with other services but try using a different (new) group and removing the old one from TFS entirely)
I have to admit I'm running out of ideas after that. If it were me, I'd try a clean install on a new server/VM and either point the new install at the old data store [multiple server setup] or export/import projects [single server setup].
For Multiple server setups, this would determine if it's a TFS installation issue/data corruption. For single-server, there's a good chance this would just clean up the problem. You could, of course, also ex/import on multi-server too if it does turn out to be a data thing.
You may want to hang on to see if someone has a less drastic solution.
Looking in the General tab of the VS Output windows there is a message:
Skipping loading group Development into Team Members because it has 102 members.
Looks like VS has a limit on here.