Jump to content


spgsitsupport

Established Members
 View Profile  See their activity

  • Posts

    198

  • Joined

  • Last visited

  • Days Won

    2

 Content Type 

Posts posted by spgsitsupport

  3. Re-run batch script daily

    in System Center Configuration Manager (Current Branch)

    Posted

    I understand, how it is supposed to work.

    But if I update the DP & then run it on a PC that never had it previously deployed then correct version is downloaded & executed (hence the version in DP is correct)

    But if I simply expect it to re-run on PC that had it previously deployed (and did run on it as part of schedule), then new .cmd is simply not downloaded & cached one is executed.

    That is what I see

  5. Re-run batch script daily

    in System Center Configuration Manager (Current Branch)

    Posted

    I have a script that I need to run daily (via Package/Program deployment). Not a problem, set it to always re-run & it does it fine at scheduled times.

    But on weekly basis the script changes (version number inside). I can re-distribute it & add another schedule, but the new .bat never makes to the client from DP

    Client keeps re-running the existing (by now old) local cache .bat

    Only way I found is to re-create whole Package/Program & deploy it again. But I find it rather drastic.

    Anybody has a better idea?

    Seb

  7. [Solved] Pause TS with cmd (not working on 1803)

    in System Center Configuration Manager (Current Branch)

    Posted

    Used it since ever to pause TS & check around 

    cmd/c start “cmd” /wait cmd

    But since using W10 1803 it simply does NOT wait!

    Instead cms get broken out instantly (without any interaction!) 

    Process completed with exit code 0
^C
Command line cmd /c start “cmd” /wait cmd returned 0
Process completed with exit code 0

    Clrl + C does NOT get invoked by keyboard!

    Anybody any ideas?

    Seb

  9. OU Collections Not Populating Entirely

    in Collections

    Posted

    Few years later & in current (latest & best) SCCM CB I have the very same issue

    Selecting AD group as criteria in query 

    select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.SecurityGroupName = "DOMAIN\\Some_Group"

    works perfectly (membership is populated)

    If I chose AD OU as criteria in query, it is hit & miss, mostly MISS 

    select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.SystemOUName = "DOMAIN_IN_FDQN/MY-COMPUTERS/SOME SUB OU/SOME OTHER SUB OU/ADMIN/THAT OFFICE" and SMS_R_System.SystemOUName = "DOMAIN_IN_FDQN/MY-COMPUTERS/SOME SUB OU/SOME OTHER SUB OU/ADMIN/THIS OFFICE"

    BOTH OU are selected from the Value box (that is the most ridiculous selection box possible!!! - can not be resized, it is too small, does not sort = total C**P)

    Yes no members are populated

    Any ideas how to get them (from OU query)

    Of course AD Discovery work fine, otherwise I could not select from that stupib box!

    Seb

  11. How can I install System Center Configuration Manager version 1702 (Current Branch) on Windows Server 2016 with SQL 2016

    in System Center Configuration Manager (Current Branch)

    Posted

    It is not the most user friendly system to upgrade/move, but a possible. PXE (if you use it) will be a problem, as the scope will be most likely the same for both

    Migration works well, but workstation object when migrated looses MAC/GUID (hence is as good as NONE - I do NOT use unknown computers and never will!), so they must be re-created (not much of an issue really)

    Applications/Packages/drivers must have source path corrected (unless you are using the same) - again easy with a script to do it en masse

    Then everything need to be redistributed (unless you do it during migration, I did not even want to think about it)

    Site change on existing clients does not work well (but a possible with a cheat - you can search for my post on MS forums)

    So a lot of work, all in all.

    Sombody can have different experiences, and if they better than mine, then well done to them!

  12. Can't Import Boot Images post upgrade to SCCM CB 1702

    in System Center Configuration Manager (Current Branch)

    Posted

    That is plain image from ADK (which is just installed, not much one can do to it!)

    I can re-create them (plain, MDT), same difference each time (no extra tabs)

    I have tried it on at least a couple of independent installs (W10 LTSB 2016 client, ADK 1703 + fix, MTD 8433, CM Admin Console 1702)

    I can edit boot images (how often does one create them anyway?!) by hand just fine, so will not waste much time on it

    Just add to another MS misteries

    Seb

    edit

    Tried with all possible combinations of ADK 1607/1703 (using .wim from either)

    None makes any difference, newly created image in CM 1702 never has any extra customization tabls!

    I can create it on client, on server itself, never fails, but also never is editable

  15. CM Power Management Plan - Wake Up Timers not working

    in System Center Configuration Manager (Current Branch)

    Posted

    CM Power Plan has an option for desktop computers

    CM_Power_Plan_-_wake_up_timesr_enabled.p

    when this is applied to collection wakeup timers are disabled! (I can enable them by hand of course - the picture below shows them enabled by hand) 

    Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>powercfg /list

Existing Power Schemes (* Active)
-----------------------------------
Power Scheme GUID: 36afc83e-6d90-4219-9f8d-622c73bb02f6  (Always On)
Power Scheme GUID: 381b4222-f694-41f0-9685-ff5bb260df2e  (Balanced)
Power Scheme GUID: 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c  (High performance)
Power Scheme GUID: a1841308-3541-4fab-bc81-f71556f20b4a  (Power saver)
Power Scheme GUID: db310065-829b-4671-9647-2261c00e86ef  (Customized Peak (ConfigMgr)) *

    CM_Power_Plan_Allow_Wake_Timers_Disabled

    I could play with GPO Registry entries, but easier is to apply script from here 

    $PowerSchemes = (powercfg.exe /LIST) | Select-String "power scheme guid" -List
$AllowWakeTimersGUID = ((powercfg.exe /q) | Select-String "(Allow wake timers)").tostring().split(" ") | where {($_.length -eq 36) -and ([guid]$_)} 
 
foreach ($PowerScheme in $PowerSchemes) {
   $PowerSchemeGUID = $PowerScheme.tostring().split(" ") | where {($_.length -eq 36) -and ([guid]$_)}
   foreach ($Argument in ("/SETDCVALUEINDEX $PowerSchemeGUID SUB_SLEEP $AllowWakeTimersGUID 1","/SETACVALUEINDEX $PowerSchemeGUID SUB_SLEEP $AllowWakeTimersGUID 1")) {
    Start-Process powercfg.exe -ArgumentList $Argument -Wait -Verb runas -WindowStyle Hidden}}

    Not an ideal, as I would expect that Enabled really means Enabled

    Anybody else noticed it?

    Seb

  16. Automatic Client Upgrade does not happen

    in System Center Configuration Manager (Current Branch)

    Posted

    No, NOT on that server/site

    It is running 2012 R2 SP1 CU4 (exactly what I upgraded to)

    In client.msi.log I get: 

    MSI (s) (18:C0) [14:12:13:255]: Windows Installer installed the product. Product Name: Configuration Manager Client. Product Version: 5.00.8239.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0.

    All good, so far, but then in ccmsetup.log there is 

    Launch from folder C:\_SMSTaskSequence\OSD\SP1000D6\
CcmSetup version: 5.0.8239.1502
Running on 'Microsoft Windows 7 Enterprise ' (6.1.7601). Service Pack (1.0). SuiteMask = 272. Product Type = 18
Ccmsetup command line: "C:\_SMSTaskSequence\OSD\SP1000D6\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\SP1000D6 /config:MobileClient.TCF /status:572:11:09	2384 (0x0950)
Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required.
Command line: "C:\_SMSTaskSequence\OSD\SP1000D6\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\SP1000D6 /config:MobileClient.TCF /status:572	2384 (0x0950)
Copying config file from C:\_SMSTaskSequence\OSD\SP1000D6\MobileClient.TCF to folder C:\WINDOWS\ccmsetup\. Return result: 0x0
.
.
.
.
.
MSI: Action 14:13:57: Rollback. Rolling back action:
File C:\WINDOWS\ccmsetup\configmgr2012ac-sp2r2sp1-kb3195483-x64.msp installation failed. Error text: ExitCode: 1603
Action: 
ErrorMessages:

    configmgr2012ac-sp2r2sp1-kb3195483-x64.msp.log shows: 

    Executing op: TypeLibraryRegister(,,FilePath=C:\WINDOWS\system32\ccmcore.dll,LibID={90C7E669-C86D-48A6-8F7A-B16521DB52BD},,,Language=0,,BinaryType=1,IgnoreRegistrationFailure=0,)
QueryPathOfRegTypeLib returned 0 in local context.	Path is 'C:\WINDOWS\system32\ccmcore.dll'
Note: 1: 1402 2: UNKNOWN\TypeLib\{90C7E669-C86D-48A6-8F7A-B16521DB52BD}\100.0\0\win32 3: 2 
CMsiServices::ProcessTypeLibrary runs in local context, not impersonated.
ProcessTypeLibraryCore returns: -2147319780. (0 means OK)
Note: 1: 2107 2: C:\WINDOWS\system32\ccmcore.dll 3: -2147319780 
Transforming table Error.
Transforming table Error.
Note: 1: 2262 2: Error 3: -2147287038
.
.
.
.
Product: Configuration Manager Client - Update 'ConfigMgr2012AC-SP2R2SP1-KB3195483-x64' could not be installed. Error code 1603. Additional information is available in the log file C:\WINDOWS\ccmsetup\Logs\configmgr2012ac-sp2r2sp1-kb3195483-x64.msp.log.
Windows Installer installed an update. Product Name: Configuration Manager Client. Product Version: 5.00.8239.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: ConfigMgr2012AC-SP2R2SP1-KB3195483-x64. Installation success or error status: 1603.
Note: 1: 1729 
Transforming table Error.
Transforming table Error.
Note: 1: 2262 2: Error 3: -2147287038 
Transforming table Error.
Transforming table Error.
Note: 1: 2262 2: Error 3: -2147287038 
Product: Configuration Manager Client -- Configuration failed.
Windows Installer reconfigured the product. Product Name: Configuration Manager Client. Product Version: 5.00.8239.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 1603.
MainEngineThread is returning 1603

    After hours of testing it seems to ONLY happen if the machine is imagined with USB media (SCCM created) in UEFI mode, but firmware does not have an option for UEFI network stack (ie Latitude  3540, has UEFI boot that works fine, but no UEFI network stack exists)

    That problem did NOT exist with previous CU2 client, so something in CU4 (client .1502 update) that causes 1603 error

    Had to revert all machines back to legacy MBR/PXE to be able to imagine them again (can use the same USB media to boot!)

    Seb

  22. Automatic Client Upgrade does not happen

    in System Center Configuration Manager (Current Branch)

    Posted

    So I followed this, but hman.log shows 

    INFO: Current client upgrade settings are: FullClientPackageID=SP100017, StagingClientPackageID=(null), ClientUpgradePackageID=SP100018, ClientUpgradeAdvertisementID=SP12000E, ClientPilotingAdvertisementID=(null), ClientUpgradeVersion=5.00.8239.1000


INFO: Full client package content hasn't been changed. Skip updating.
INFO: Client upgrade package content hasn't been changed. Skip updating.

    Which is plain wrong as the client is (in CU4) 5.0.8239.1502

  23. Automatic Client Upgrade does not happen

    in System Center Configuration Manager (Current Branch)

    Posted

    I can see in the log 

    Execution Request for advert SP12000E package SP100018 program Configuration Manager Client Upgrade Program state change from WaitingContent to WaitingContent
Persisting request for program Configuration Manager Client Upgrade Program package SP100018 in state WaitingContent

    But such advert for Package SP100018 = Configuration Manager Client Upgrade Package no longer seems to exist in the site

    Used PowerShell Script to locate SCCM objects in SCCM console 

    PS C:\PSScripts> .\Locate-SCCMObject.ps1 SCCM-server SP100018
Object Type: Unknown
Console Path: Academic Departments

    Or Content Library Explorer:

    invalid.png

    So now I can not get client upgraded to latest CU4 KB3195483 version via Automatic client upgrades

    Any idea how to fix it?

    Seb

  25. SQL version detection and reporting in SCCM ?

    in System Center Configuration Manager (Current Branch)

    Posted

    There is this:

    https://sccm-zone.com/sql-version-detection-and-report-sccm-2012-r2-12f299b5e63b

    which is inaccurate in places.

    Supplied .rdl is unusable (at least on RS 2012 R2) die to:

    https://connect.microsoft.com/SQLServer/feedback/details/2050151/rdl-2016-schema-moved-taken-down

    Kind of solution is here:

    https://stackoverflow.com/questions/36272514/the-report-definition-has-an-invalid-target-namespace-rsinvalidreportdefinition

    but still does not work: 

    The definition of this report is not valid or supported by this version of Reporting Services. The report definition may have been created with a later version of Reporting Services, or contain content that is not well-formed or not valid based on Reporting Services schemas. Details: The element 'Report' in namespace 'http://schemas.microsoft.com/sqlserver/reporting/2010/01/reportdefinition' has invalid child element 'Body' in namespace 'http://schemas.microsoft.com/sqlserver/reporting/2010/01/reportdefinition'. List of possible elements expected: 'Description, Author, AutoRefresh, InitialPageName, DataSources, DataSets, ReportParameters, Code, EmbeddedImages, Language, CodeModules, Classes, CustomProperties, Variables, DeferVariableEvaluation, ConsumeContainerWhitespace, DataTransform, DataSchema, DataElementName, DataElementStyle, ReportSections' in namespace 'http://schemas.microsoft.com/sqlserver/reporting/2010/01/reportdefinition' as well as any element in namespace '##other'. (rsInvalidReportDefinition)

    Anybody knows a solution that can be easily implemented?

    Thanks

    Seb

     

    edit:

    Also tried https://gallery.technet.microsoft.com/scriptcenter/SQL-Version-Report-in-SCCM-61d46820

    Imports fine to SSRS, but on running I get error 

    An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset 'DataSet1'. (rsErrorExecutingCommand)
For more information about this error navigate to the report server on the local server machine, or enable remote errors

     

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.