
M13LU
Established Members-
Posts
3 -
Joined
-
Last visited
M13LU's Achievements
Newbie (1/14)
0
Reputation
-
Hello everybody, I need to create an application that has different msi parameters depending on the VLAN the server is in. I thought i would use different Deployment types and determine the subnet by using a custom Global Condition. I started with creating a global condition using a powershell command (Get-NetIPConfiguration | Where-Object {$_.IPv4DefaultGateway}).IPv4DefaultGateway.nexthop this returns the ip address of the gateway but found out that this would only work on windows 2012r2 and above. There are still some 2008r2 servers here, so no good. I then decided to use a WMI query and tested it on every os. Get-WmiObject -Query "select DefaultipGateway from win32_networkadapterconfiguration where ipenabled='true'" created a wql query as Global Condition then created my requirement but when i try and deploy the application, it doesn't work. where am i going wrong here?
- 1 reply
-
- mandatory profiles
- wondows 10
-
(and 36 more)
Tagged with:
- mandatory profiles
- wondows 10
- cb1910
- sccm
- cross-forest
- multi-domain
- sccm
- cmg
- azure
- sup
- client
- sccm
- dp
- office 365 updates
- query or collection in sccm
- gpo
- sccm cb
- database
- sccm cmdlets
- sccm client
- powershell
- wmi
- sccm
- client settings
- console
- dell
- 7212
- imaging
- osd
- defaultuser0
- configmgr
- sccm
- admin tools
- current branch
- manageengine
- patch connect plus
- configuration manager
- non microsoft updates
-
Have you tried using CCMCLEAN.EXE? its a tool to completely removes any trace of the SCCM agent. it was part of the sccm 2003 toolkit but still works. after that reinstall the agent
-
Hello, I'm having a weird issue on a SCCM 2012 R2 installation. When i create a configuration baseline, the name is show as blank and the baseline is disabled. (as shown below) when i look at the properties of the baseline all the info is correct.(as shown below) but when i try and enable the baseline it doesn't work. SMSProv.log shows the following. which makes me believe it might be an issue with either wmi or access to the db If I copy the sql query from the log : select all SMS_ConfigurationBaselineInfo.CI_ID,SMS_ConfigurationBaselineInfo.LocaleID,SMS_ConfigurationBaselineInfo.ActivatedCount,SMS_ConfigurationBaselineInfo.ApplicabilityCondition,SMS_ConfigurationBaselineInfo.AssignedCount,SMS_ConfigurationBaselineInfo.CI_ID,SMS_ConfigurationBaselineInfo.CI_UniqueID,SMS_ConfigurationBaselineInfo.CIType_ID,SMS_ConfigurationBaselineInfo.CIVersion,SMS_ConfigurationBaselineInfo.ComplianceCount,SMS_ConfigurationBaselineInfo.CompliantPercentage,SMS_ConfigurationBaselineInfo.CreatedBy,SMS_ConfigurationBaselineInfo.DateCreated,SMS_ConfigurationBaselineInfo.DateLastModified,SMS_ConfigurationBaselineInfo.EffectiveDate,SMS_ConfigurationBaselineInfo.EULAAccepted,SMS_ConfigurationBaselineInfo.EULAExists,SMS_ConfigurationBaselineInfo.EULASignoffDate,SMS_ConfigurationBaselineInfo.EULASignoffUser,SMS_ConfigurationBaselineInfo.IsUserCI,SMS_ConfigurationBaselineInfo.FailureCount,SMS_ConfigurationBaselineInfo.InUse,SMS_ConfigurationBaselineInfo.IsAssigned,SMS_ConfigurationBaselineInfo.IsBroken,SMS_ConfigurationBaselineInfo.IsBundle,SMS_ConfigurationBaselineInfo.IsEnabled,SMS_ConfigurationBaselineInfo.IsHidden,SMS_ConfigurationBaselineInfo.IsQuarantined,SMS_ConfigurationBaselineInfo.IsUserDefined,SMS_ConfigurationBaselineInfo.LastModifiedBy,SMS_ConfigurationBaselineInfo.Description,SMS_ConfigurationBaselineInfo.DisplayName,SMS_ConfigurationBaselineInfo.CIInformativeURL,SMS_ConfigurationBaselineInfo.LocaleID,SMS_ConfigurationBaselineInfo.ModelName,SMS_ConfigurationBaselineInfo.NonComplianceCount,SMS_ConfigurationBaselineInfo.PermittedUses,SMS_ConfigurationBaselineInfo.SDMPackageVersion,SMS_ConfigurationBaselineInfo.Severity,SMS_ConfigurationBaselineInfo.SourceSite,SMS_ConfigurationBaselineInfo.TargetCompliance from fn_ListConfigurationBaselineInfo_List(1033) AS SMS_ConfigurationBaselineInfo where SMS_ConfigurationBaselineInfo.CI_ID = 16851006 I get to see the correct information, the name and everything are normal characters as i had entered them. when i run the wmi query i get the following result: Does anybody here have an idea what to do? how to fix this. would an update maybe fix this?