未加星标

DSC Use Configuration in Multiple Environments (PSDSCRunAsCredential)

字体大小 | |
[系统(windows) 所属分类 系统(windows) | 发布者 店小二04 | 时间 2016 | 作者 红领巾 ] 0人收藏点击收藏

In PowerShell 5.0 Microsoft introduced a new property PSDSCRunAsCredential . This property allows you to run your DSC resource under specific credentials. If you do not specify anything the DSC agent or LocalConfigurationManager (LCM) performs any operation in the LocalSystem context. In most cases this is good enough and provides enough permission to fulfill its task. But there are scenarios where you need e.g. the script resource to configure certain tasks on the server which require domain credentials. This could be e.g. creating a Group Managed Service Account (gMSA) in your domain and adding it to your server. If you would try to run this script resource using LocalSystem you are not able to authenticate against Active Directory and the script fails. Because to create and install a gMSA you need to authenticate against Active Directory. If go a step further and let’s assume you want to use the same DSC configuration in two different domains Domain A and Domain B. This means you would need to run the script resource under two different domain credentials, otherwise you would not be able to run the script. This is when the PSDSCRunAsCredential property comes into play.

Here a simple example how you could use ONE configuration to run in TWO different environments. The following TestScript consumes two credentials $MastaCredential and $OtherCredential. If the computer which runs the DSC configuration is joined to the masta.ad domain the script resource should be executed under $MastaCredential, if it is another domain it should use $OtherCredential. To visualize which user is executing the script I used Write-Verbose $env:USERNAME which will expose the current user.

$MastaCredential = Get-Credential
$OtherCredential = Get-Credential
$ConfigData = @{
AllNodes = @(
@{
NodeName = "localhost"
PSDscAllowPlainTextPassword = $true
MastaUser = $MastaCredential
OtherUser = $OtherCredential
}
)
}
Configuration TestScript {
Node $AllNodes.NodeName
{Script ChangeUser{
SetScript =
{
Write-Verbose $env:USERNAME
}
TestScript =
{ $false
}
GetScript =
{
Write-Verbose $env:USERNAME
}
PsDscRunAsCredential = if ((Get-WmiObject Win32_ComputerSystem).Domain -ieq 'masta.ad' ) {$Node.MastaUser} else {$Node.OtherUser}}
}
}
TestScript -ConfigurationData $ConfigData -OutputPath c:\Temp
Start-DscConfiguration -Wait -Force -Verbose c:\Temp

If I run the configuration on a computer in the masta.ad domain it will run under MastaUser…


DSC   Use Configuration in Multiple Environments (PSDSCRunAsCredential)

If I simulate a different domain (change the if statement so it does not match the domain name) a different user is used in my case OtherUser…


DSC   Use Configuration in Multiple Environments (PSDSCRunAsCredential)

Having just a simple if statement in combination with the PSDSCRunAsCredential property in place, let’s you use the script resource (or any other resource) in different environments where domain credentials are required.

I think it is a very cool approach!

本文系统(windows)相关术语:三级网络技术 计算机三级网络技术 网络技术基础 计算机网络技术

主题: PowerShell
分页:12
转载请注明
本文标题:DSC Use Configuration in Multiple Environments (PSDSCRunAsCredential)
本站链接:http://www.codesec.net/view/481665.html
分享请点击:


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 系统(windows) | 评论(0) | 阅读(32)