All Activity
This stream auto-updates
- Today
-
ok well you can always post your smsts.log here and we'll advise -
Hi, All clients have been updated. client version is now 5.00.8790.1025 I tried manually uninstalling the client then re-pushing it from SCCM and this then updated all the policies and the applications started coming down. I'm not sure if part of the issue was DNS? I'm also trying to use the windows servicing for windows 10 but no updates are coming out to the client machines. What would be the best log files to check for these two issues and are they on the SCCM server or the client machines? -
We are getting ready to get rid of our AV solution and are looking to use SCCM Endpoint Protection instead. Is this enough? Are we still going to be protected as we were with a full blown AV? We are fully Windows 10 going forward. Is there a document that will walk me through setting this all up? Is there a way to setup email alerts when a virus / malware / other security alert is found? Anything else we need to know before starting?
-
Once I cleared out all the drivers from Boot Image (x64) it allowed me to boot into SCCM again. Now I'm back to errors on the task sequence, but at least the devices will image again. New problem for a new day, but as far as this specific fault goes, it is resolved thank you. -
Orphaned Distribution Points
anyweb replied to Ann's topic in System Center Configuration Manager (Current Branch)
take a look at the following post and scroll down for Orphaned Content. https://www.niallbrady.com/2017/01/24/what-is-the-contentlibrarycleanup-tool-and-how-can-i-use-it/ -
SCCM SQL Backup Failures
anyweb replied to Ann's topic in System Center Configuration Manager (Current Branch)
is it shared storage ? " Consider reducing the IO load on the system or choose a shadow storage copy volume that is not being shadow copied. " -
We have just done a site refresh and replaced several site servers, I seem to have orphaned distribution points in my CB1810 environment. The SMS_Distribution_Point_Monitoring keeps trying to validate some packages on servers that no longer exist in the environment and haven't for a while. I have tried to use the sql select commands that used to be used in SCCM 2012 and 2007 but these are giving me 0 records. My SMS_Site_System component is always failing to process files from these old DP's saying it contains errors or invalid data. Is there a different way to handle Orphaned DP's in CB? -
Setup:Single Primary Server: Windows Server 2012 R2Remote SQL Cluster Server: Windows Server 2012 R2ConfigMgr version: CB 1810 (KB4490434)Issue:Last complete ConfigMgr Maintenance Task Backup was early hours 30/05/2019Updates installed on the SQL Server: KB4495586, KB4495615, KB4499165, KB4495585, KB4495608, KB4498206, KB4499151. These were installed on the evening of 30/05/2019Since last backup on 30/05/2019 the ConfigMgr Backup has constantly been failing with the following messages:Message ID: 5052, Description: SMS SQL Backup service on the SQL Server *** failed to backup the site database ***, Failed: The error reported by the service is error: CopyFile to *** failed: [error code 2: the system can not find the file specified]. Backup is not complete.Message ID: 5048, Description: Site Backup Failed while trying to copy the files to the destination. Backup operation is not complete. Possible Cause: The volume shadow copy service may not have sufficient disk space to create the shadow copy of the site backup snapshot information.On the SQL Server each time an Event error is created:EventID: 25, Source: Volsnap, Description: The shadow copies of volume E:\Data were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow storage copy volume that is not being shadow copied.We have rebooted both the Primary and the SQL Servers and also attempted the backup at different times of day.Has anybody seen this issue before or any advice on best way to resolve this issue?
-
Thank you. Really great guide! -
It's still in progress, these guides take time to write, please be patient... i'll update here when it's done, thanks !
- Yesterday
-
Is there a way to create multiple Deployment Types under one application. I am using Add-CMScriptDeploymentType and get an error on the second one. Add-CMScriptDeploymentType : ConfigMgr Error Object: instance of SMS_ExtendedStatus { Description = "The digest is not valid"; ErrorCode = 1078462235; File = "..\\sspconfigurationitem.cpp"; Line = 1980; Operation = "PutInstance"; ParameterInfo = ""; ProviderName = "ExtnProv"; SQLMessage = "[42000][3998][Microsoft] [SQL Server]Uncommittable transaction is detected at the end of the batch. The transaction is rolled back."; SQLSeverity = 16; SQLStatus = 3998; StatusCode = 2147749889; }; At C:\Install\CreateTKA.ps1:252 char:11 + Add-CMScriptDeploymentType -ApplicationName $ApplicationNam ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (Microsoft.Confi...mentTypeCommand:AddScriptDeploymentTypeCommand) [Add-CM ScriptDeploymentType], WqlQueryException + FullyQualifiedErrorId : UnhandledException,Microsoft.ConfigurationManagement.Cmdlets.AppMan.Commands.AddScriptDe ploymentTypeCommand
-
Thanks for the reply issue started when i converted the Secondary Site to a Distribution Point -
80072ee2 = timeout This is almost always a firewall / network issues. -
Hi All, Sorry if this is has already been discussed, I look after a global SCCM Environment, 1 CAS Server, 2 Primary Sites and 40+ Distribution Points. OSD: Some of our clients in the US are unable to retrieve policy due to a Time Sync with the primary site. SMSTS.log on an affected client states the following: Failed to get Client Identity (80072ee2) SyncTimeWithMP() failed 80072ee2 Failed to get time information from MP: http:\\xxxxxxxxxxxx The US Primary Site is set to UTC Eastern Time -05:00. Clients with timezone UTC Pacific Time -08:00 seem to be affected. How can i support both timezones? Thanks Matt
-
try updating your boot wim(s) to the distribution points again, to make sure they get injected with all the new binaries from the SCCM 1902 upgrade.
-
Hi Niall, Haven't used a VM since I set everything up over a year ago to be honest as I've always been able to tweak the image slightly every time I've needed to add something to the task sequence. These are machines that have always worked, so I just went to run the task sequence again. I can't even deploy the existing task sequences that I've been using since last year. Other than installing 1902, the latest ADK, PE and running Update Distribution Points on the Boot 64 image I haven't changed a thing. Ulitmately what I'm trying to do is push out Windows 10 1903. Up until this update I was installing 1803 without issue. I'll put a VM together now to test it out though.
-
it seems like you have PXE booted and SCCM detects three USB drives and no local drive, is that correct, can you tell me a bit more about how you are testing here ? why are you not trying to test this with virtual machines ? also, if you are indeed testing on real hardware that is not detecting the hdd, then have you added any storage drivers for the chipset to your boot wim ? cheers niall
-
Is part 7 onwards complete yet neither the link at the top or bottom of part 6 is active link. Thanks in advance.
-
SCCM Failed Boot log - Copy.log
-
it's not enough to go on, please copy the smsts.log file from x to your usb drive and attach it here.
-
Please see that attached image.
-
enable diagnostic support in your boot wim, then press f8 at the pxe password screen, in the cmd prompt use cmtrace x:\windows\temp\smstslog\smsts.log and review the failures in red to see why it's having issues, if you can attach the smsts.log file here that would help or if you cannot, then attach screenshots of the errors highlighted in SMSTS.log
-
First apologies if there is already a thread for this, I have been unable to find one. I have just upgraded my SCCM to 1902, I have installed the latest ADK, I've installed the latest PE and then I updated my boot image. What I cannot understand is that when I PXE boot a new client, it almost makes it to the Enter Password and then the client reboots. I've tried three different models of machine and I get the exact same problem. Any advise would be most welcome. Thanks in advance!
-
dear all we are staging with windows version 1809 On the win pe part we've integraded the displaylink lan drivers and we recieve an ip problem is after the winpe part, the usb adapter is losing connection and doesnt reinitialise We've integraded the dell proposition to do a usb port reset using devcon, but this doesnt work if somebody has the same problem? portable is a dell latitude 5300 2-in-1 and universal docking is a kensington sd3500v (with displaylink drivers) thank you all Bart - Last week
-
There is no need to mess with the msi. Just create a installer script that uninstalls the application if it is installed and immediatelly reinstalls it. Additionally create a new detection rule for the install date property in the uninstall registry key with a value of >= current datetime.
