Jump to content


radish

Established Members
  • Posts

    79
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by radish

  1. 1.thumb.jpg.768888a886d2480a2819e725766165d7.jpg

     

     

    Guānyú_SMSTasksequence wénjiàn jiā shìfǒu biànliàng mìnglìng lái dàitì? Yòng mdt fābùle yīgè qūdòng bāo rúhé zhǐdìng mìnglìng lù jìn zhíxíng suǒzài chéngxù,_SMSTasksequence\packages\12000061\EasyDrv7_Win7.X86.Exe/Fa, wǒ fāxiàn zhège_SMSTasksequence wénjiàn jiā yǒu shíhòu huì zài zuìdà défēn qū lǐmiàn, bǐrú shì C.D huòzhě E wǒ gāi rúhé zhǔnquè zhíxíng_SMSTasksequence\packages\12000061\EasyDrv7_Win7.X86.Exe/Fa ne?
    展开
     
    246/5000
     
     

    关于_SMSTasksequence文件夹 是否变量命令 来代替?
    用mdt发布了一个驱动包

    如何指定命令路劲 执行所在程序,_SMSTasksequence\packages\12000061\EasyDrv7_Win7.x86.exe /Fa,
     我发现这个_SMSTasksequence文件夹有时候会在最大得分区里面,比如是C 。D或者E
    我该如何准确执行_SMSTasksequence\packages\12000061\EasyDrv7_Win7.x86.exe /Fa 呢?

    About the _SMSTasksequence folder Is the variable command instead?
    Released a driver package with mdt

    How to specify the command path to execute the program, _SMSTasksequence\packages\12000061\EasyDrv7_Win7.x86.exe /Fa,
      I found that this _SMSTasksequence folder is sometimes in the largest scoring area, such as C. D or E
    How can I accurately execute _SMSTasksequence\packages\12000061\EasyDrv7_Win7.x86.exe /Fa?

     

     

     

    2.jpg

  2. 5 hours ago, radish said:

     

     

    非常感谢您的帮助。但是,我只想将USMT用户状态信息传输到WinPE的下的服务器,我暂时不需要使用的BitLocker。

    只需配置此MDT 2013,您可以使用彩信吗?
    将MDT 2013与Configuration Manager 2012 R2集成 - 指南


    无需再配置MBAM了吗?
    安装和配置MBAM 2.0或更高版本-指南1,2指南
    安装和配置MAIK Kosters博士Web服务-指南(不要忘记安装ASP.NET 3.5和相关的ISAPI扩展)

    88.thumb.png.608a07b1cc2558eef0148d6df096d6ad.png

     

    目前SCCM版本是SCCM1902和MDT2013 update2插件

    The current SCCM version is SCCM1902 and MDT2013 update2 plugin.

    这个MMS-2016-Windows-10-UEFI-BitLocker-HTA 是替换旧The CM12 BitLocker FrontEnd HTA  哪些得对应文件夹目录?

    This MMS-2016-Windows-10-UEFI-BitLocker-HTA is the replacement of the old The CM12 BitLocker FrontEnd HTA which corresponds to the folder directory?

  3. 4 hours ago, anyweb said:

    ok so you want to transfer data using USMT while in WinPE to a state store, you could use my prebuilt HTA to help with that, it even works with BitLocker if you have an MBAM back end.

    https://www.niallbrady.com/2016/05/17/introducing-the-windows-10-uefi-bitlocker-frontend-for-system-center-configuration-manager-current-branch/

     

     

    Thank you very much for your help. However, I only want to transfer the usmt user status information to the server under winpe, and I don't need to use BitLocker for the time being.

    Just configure this MDT 2013, can you use MMS?
    Integrate MDT 2013 with Configuration Manager 2012 R2 - Guide


    No need to configure MBAM anymore? ? !
    Install and configure MBAM 2.0 or later - Guide 1, Guide 2.
    Install and configure Maik Kosters web services - Guide (don't forget to install ASP.NET 3.5 and associated ISAPI extensions)

  4. Excuse me, I want to start the OS image after the computer presses F12 pxe to capture the user data and transfer it to the server instead of formatting the disk installation system immediately.
    This method is useful when transferring data sometimes when the computer system can't get in.
    How is this set up?

     

    11.thumb.jpg.84e5e80fa1e257af6682fe02f3f8c0f0.jpg

     

    According to this setting, it seems that the user settings are not captured first, but the application deployment is started directly.

  5. 1375846

     

    域环境 Win2012R2

    exchange2016CU11 ISO

    First step expansion is no problem

    第一步骤扩展没问题 

    .\Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

     

    The second step is to expand the organization name.

    第二步骤扩展组织名称就有问题了

    .\Setup.exe /PrepareAD /OrganizationName:"lab" /IAcceptExchangeServerLicenseTerms

    附上日志链接

    链接:日志文件
    提取码:3jy9 

    请问这是怎么回事?域环境2012R2也没装杀毒软件。

     

    Attach a log link

    Link: log file
    Extraction code: 3jy9

    May I ask how is this going? The domain environment 2012R2 also does not have anti-virus software installed.

     

    Part of the log record is as follows

    部分日志记录如下

     

    [12-31-2018 13:33:29.0292] [2] 'New-ApprovalApplicationContainer'的 Active Directory 会话设置是: 查看整个林:'True', 配置域控制器:“DC03.sztlyy.net”, 首选全局编录:“DC03.sztlyy.net”, 首选域控制器:“{ DC03.sztlyy.net }”
    [12-31-2018 13:33:29.0292] [2] User specified parameters:  -DomainController:'DC03.sztlyy.net'
    [12-31-2018 13:33:29.0292] [2] Beginning processing new-ApprovalApplicationContainer
    [12-31-2018 13:33:29.0295] [2] Processing object "Approval Applications".
    [12-31-2018 13:33:29.0298] [2] The object 'Approval Applications' already exists.
    [12-31-2018 13:33:29.0299] [2] Ending processing new-ApprovalApplicationContainer
    [12-31-2018 13:33:29.0300] [1] Executing: 
              $rpt = @(Get-RetentionPolicyTag -IncludeSystemTags -DomainController $RoleDomainController | where {$_.Name -eq 'AutoGroup'});
              new-ApprovalApplication -AutoGroup -ELCRetentionPolicyTag $rpt[0].Identity -DomainController $RoleDomainController;
            
    [12-31-2018 13:33:29.0302] [2] 'Get-RetentionPolicyTag'的 Active Directory 会话设置是: 查看整个林:'True', 配置域控制器:“DC03.sztlyy.net”, 首选全局编录:“DC03.sztlyy.net”, 首选域控制器:“{ DC03.sztlyy.net }”
    [12-31-2018 13:33:29.0302] [2] User specified parameters:  -IncludeSystemTags:'True' -DomainController:'DC03.sztlyy.net'
    [12-31-2018 13:33:29.0302] [2] Beginning processing Get-RetentionPolicyTag
    [12-31-2018 13:33:29.0303] [2] Searching objects of type "RetentionPolicyTag" with filter "$null", scope "SubTree" under the root "$null".
    [12-31-2018 13:33:29.0303] [2] Request filter in Get Task: (&(objectCategory=msExchELCFolder)(msExchVersion>=1125899906842624)(msExchVersion<=2251799813685248)(!(msExchVersion=2251799813685248))).
    [12-31-2018 13:33:29.0312] [2] Previous operation run on domain controller 'DC03.sztlyy.net'.
    [12-31-2018 13:33:29.0312] [2] Preparing to output objects. The maximum size of the result set is "Unlimited".
    [12-31-2018 13:33:29.0339] [2] Ending processing Get-RetentionPolicyTag
    [12-31-2018 13:33:29.0345] [2] 'New-ApprovalApplication'的 Active Directory 会话设置是: 查看整个林:'True', 配置域控制器:“DC03.sztlyy.net”, 首选全局编录:“DC03.sztlyy.net”, 首选域控制器:“{ DC03.sztlyy.net }”
    [12-31-2018 13:33:29.0345] [2] User specified parameters:  -AutoGroup:'True' -ELCRetentionPolicyTag:'AutoGroup' -DomainController:'DC03.sztlyy.net'
    [12-31-2018 13:33:29.0345] [2] Beginning processing new-ApprovalApplication
    [12-31-2018 13:33:29.0347] [2] Processing object "AutoGroup".
    [12-31-2018 13:33:29.0349] [2] The object 'AutoGroup' already exists.
    [12-31-2018 13:33:29.0349] [2] Ending processing new-ApprovalApplication
    [12-31-2018 13:33:29.0351] [1] Executing: 
              $rpt = @(Get-RetentionPolicyTag -IncludeSystemTags -DomainController $RoleDomainController | where {$_.Name -eq 'ModeratedRecipients'});
              new-ApprovalApplication -ModeratedRecipients -ELCRetentionPolicyTag $rpt[0].Identity -DomainController $RoleDomainController;
            
    [12-31-2018 13:33:29.0353] [2] 'Get-RetentionPolicyTag'的 Active Directory 会话设置是: 查看整个林:'True', 配置域控制器:“DC03.sztlyy.net”, 首选全局编录:“DC03.sztlyy.net”, 首选域控制器:“{ DC03.sztlyy.net }”
    [12-31-2018 13:33:29.0353] [2] User specified parameters:  -IncludeSystemTags:'True' -DomainController:'DC03.sztlyy.net'
    [12-31-2018 13:33:29.0353] [2] Beginning processing Get-RetentionPolicyTag
    [12-31-2018 13:33:29.0354] [2] Searching objects of type "RetentionPolicyTag" with filter "$null", scope "SubTree" under the root "$null".
    [12-31-2018 13:33:29.0354] [2] Request filter in Get Task: (&(objectCategory=msExchELCFolder)(msExchVersion>=1125899906842624)(msExchVersion<=2251799813685248)(!(msExchVersion=2251799813685248))).
    [12-31-2018 13:33:29.0360] [2] Previous operation run on domain controller 'DC03.sztlyy.net'.
    [12-31-2018 13:33:29.0360] [2] Preparing to output objects. The maximum size of the result set is "Unlimited".
    [12-31-2018 13:33:29.0389] [2] Ending processing Get-RetentionPolicyTag
    [12-31-2018 13:33:29.0391] [2] 'New-ApprovalApplication'的 Active Directory 会话设置是: 查看整个林:'True', 配置域控制器:“DC03.sztlyy.net”, 首选全局编录:“DC03.sztlyy.net”, 首选域控制器:“{ DC03.sztlyy.net }”
    [12-31-2018 13:33:29.0391] [2] User specified parameters:  -ModeratedRecipients:'True' -ELCRetentionPolicyTag:'ModeratedRecipients' -DomainController:'DC03.sztlyy.net'
    [12-31-2018 13:33:29.0391] [2] Beginning processing new-ApprovalApplication
    [12-31-2018 13:33:29.0392] [2] Processing object "ModeratedRecipients".
    [12-31-2018 13:33:29.0393] [2] The object 'ModeratedRecipients' already exists.
    [12-31-2018 13:33:29.0393] [2] Ending processing new-ApprovalApplication
    [12-31-2018 13:33:29.0395] [1] Processing component 'Unified Messaging Global AD Configuration' (正在配置全局统一消息设置。).
    [12-31-2018 13:33:29.0396] [1] Executing: 
              install-Container -Name "UM DialPlan Container" -DomainController $RoleDomainController
              Initialize-UMDialPlanContainerPermission
            
    [12-31-2018 13:33:29.0397] [2] 'install-Container'的 Active Directory 会话设置是: 查看整个林:'True', 配置域控制器:“DC03.sztlyy.net”, 首选全局编录:“DC03.sztlyy.net”, 首选域控制器:“{ DC03.sztlyy.net }”
    [12-31-2018 13:33:29.0397] [2] User specified parameters:  -Name:'UM DialPlan Container' -DomainController:'DC03.sztlyy.net'
    [12-31-2018 13:33:29.0397] [2] Beginning processing install-Container
    [12-31-2018 13:33:29.0398] [2] Processing object "UM DialPlan Container".
    [12-31-2018 13:33:29.0400] [2] Ending processing install-Container
    [12-31-2018 13:33:29.0401] [2] 'Initialize-UMDialPlanContainerPermission'的 Active Directory 会话设置是: 查看整个林:'True', 配置域控制器:“DC03.sztlyy.net”, 首选全局编录:“DC03.sztlyy.net”, 首选域控制器:“{ DC03.sztlyy.net }”
    [12-31-2018 13:33:29.0401] [2] User specified parameters: 
    [12-31-2018 13:33:29.0401] [2] Beginning processing Initialize-UMDialPlanContainerPermission
    [12-31-2018 13:33:29.0403] [2] Used domain controller DC03.sztlyy.net to read object DC=sztlyy,DC=net.
    [12-31-2018 13:33:29.0408] [2] Used domain controller DC03.sztlyy.net to read object CN=Delegated Setup1,OU=Microsoft Exchange Security Groups,DC=sztlyy,DC=net.
    [12-31-2018 13:33:29.0412] [2] Adding access control entries to the security descriptor for the object CN=UM DialPlan Container,CN=lab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=sztlyy,DC=net.
    [12-31-2018 13:33:29.0414] [2] [WARNING] The appropriate access control entry is already present on the object "CN=UM DialPlan Container,CN=lab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=sztlyy,DC=net" for account "SZTLYY\Delegated Setup1".
    [12-31-2018 13:33:29.0415] [2] Ending processing Initialize-UMDialPlanContainerPermission
    [12-31-2018 13:33:29.0416] [1] Executing: 
    install-Container -Name "UM IPGateway Container" -DomainController $RoleDomainController


    [12-31-2018 13:33:29.0421] [2] 'install-Container'的 Active Directory 会话设置是: 查看整个林:'True', 配置域控制器:“DC03.sztlyy.net”, 首选全局编录:“DC03.sztlyy.net”, 首选域控制器:“{ DC03.sztlyy.net }”
    [12-31-2018 13:33:29.0421] [2] User specified parameters:  -Name:'UM IPGateway Container' -DomainController:'DC03.sztlyy.net'
    [12-31-2018 13:33:29.0422] [2] Beginning processing install-Container
    [12-31-2018 13:33:29.0422] [2] Processing object "UM IPGateway Container".
    [12-31-2018 13:33:29.0424] [2] Ending processing install-Container
    [12-31-2018 13:33:29.0426] [1] Executing: 
    install-Container -Name "UM AutoAttendant Container" -DomainController $RoleDomainController


    [12-31-2018 13:33:29.0427] [2] 'install-Container'的 Active Directory 会话设置是: 查看整个林:'True', 配置域控制器:“DC03.sztlyy.net”, 首选全局编录:“DC03.sztlyy.net”, 首选域控制器:“{ DC03.sztlyy.net }”
    [12-31-2018 13:33:29.0428] [2] User specified parameters:  -Name:'UM AutoAttendant Container' -DomainController:'DC03.sztlyy.net'
    [12-31-2018 13:33:29.0428] [2] Beginning processing install-Container
    [12-31-2018 13:33:29.0428] [2] Processing object "UM AutoAttendant Container".
    [12-31-2018 13:33:29.0436] [2] Ending processing install-Container
    [12-31-2018 13:33:29.0438] [1] Processing component 'CAFE Global AD Configuration' (正在配置全局客户端访问设置。).
    [12-31-2018 13:33:29.0438] [1] Processing component 'Domain-specific AD Configuration' (正在为 Exchange 配置域。).
    [12-31-2018 13:33:29.0439] [1] Executing: 
              $createTenantRoot = ($RoleIsDatacenter -or $RoleIsPartnerHosted);
              $createMsoSyncRoot = $RoleIsDatacenter;

              #$RoleDatacenterIsManagementForest is set only in Datacenter deployment; interpret its absense as $false
              [bool]$isManagementForest = ($RoleDatacenterIsManagementForest -eq $true);

              if ($RolePrepareAllDomains)
              {
                  initialize-DomainPermissions -AllDomains:$true -CreateTenantRoot:$createTenantRoot -CreateMsoSyncRoot:$createMsoSyncRoot -IsManagementForest:$isManagementForest;
              }
              elseif ($RoleDomain -ne $null)
              {
                  initialize-DomainPermissions -Domain $RoleDomain -CreateTenantRoot:$createTenantRoot -CreateMsoSyncRoot:$createMsoSyncRoot -IsManagementForest:$isManagementForest;
              }
              else
              {
                  initialize-DomainPermissions -CreateTenantRoot:$createTenantRoot -CreateMsoSyncRoot:$createMsoSyncRoot -IsManagementForest:$isManagementForest;
              }
            
    [12-31-2018 13:33:29.0444] [2] 'initialize-DomainPermissions'的 Active Directory 会话设置是: 查看整个林:'True', 配置域控制器:“DC03.sztlyy.net”, 首选全局编录:“DC03.sztlyy.net”, 首选域控制器:“{ DC03.sztlyy.net }”
    [12-31-2018 13:33:29.0444] [2] User specified parameters:  -CreateTenantRoot:'False' -CreateMsoSyncRoot:'False' -IsManagementForest:'False'
    [12-31-2018 13:33:29.0444] [2] Beginning processing initialize-DomainPermissions
    [12-31-2018 13:33:29.0448] [2] Used domain controller DC03.sztlyy.net to read object DC=sztlyy,DC=net.
    [12-31-2018 13:33:29.0451] [2] Used domain controller DC03.sztlyy.net to read object CN=Exchange Servers1,OU=Microsoft Exchange Security Groups,DC=sztlyy,DC=net.
    [12-31-2018 13:33:29.0451] [2] Used domain controller DC03.sztlyy.net to read object CN=Exchange Servers1,OU=Microsoft Exchange Security Groups,DC=sztlyy,DC=net.
    [12-31-2018 13:33:29.0455] [2] Used domain controller DC03.sztlyy.net to read object CN=Organization Management1,OU=Microsoft Exchange Security Groups,DC=sztlyy,DC=net.
    [12-31-2018 13:33:29.0455] [2] Used domain controller DC03.sztlyy.net to read object CN=Organization Management1,OU=Microsoft Exchange Security Groups,DC=sztlyy,DC=net.
    [12-31-2018 13:33:29.0458] [2] Used domain controller DC03.sztlyy.net to read object CN=Public Folder Management1,OU=Microsoft Exchange Security Groups,DC=sztlyy,DC=net.
    [12-31-2018 13:33:29.0459] [2] Used domain controller DC03.sztlyy.net to read object CN=Public Folder Management1,OU=Microsoft Exchange Security Groups,DC=sztlyy,DC=net.
    [12-31-2018 13:33:29.0462] [2] Used domain controller DC03.sztlyy.net to read object CN=Exchange Trusted Subsystem1,OU=Microsoft Exchange Security Groups,DC=sztlyy,DC=net.
    [12-31-2018 13:33:29.0462] [2] Used domain controller DC03.sztlyy.net to read object CN=Exchange Trusted Subsystem1,OU=Microsoft Exchange Security Groups,DC=sztlyy,DC=net.
    [12-31-2018 13:33:29.0465] [2] Used domain controller DC03.sztlyy.net to read object CN=Exchange Windows Permissions1,OU=Microsoft Exchange Security Groups,DC=sztlyy,DC=net.
    [12-31-2018 13:33:29.0465] [2] Used domain controller DC03.sztlyy.net to read object CN=Exchange Windows Permissions1,OU=Microsoft Exchange Security Groups,DC=sztlyy,DC=net.
    [12-31-2018 13:33:29.0467] [2] Used domain controller DC03.sztlyy.net to read object CN=Domain Users,CN=Users,DC=sztlyy,DC=net.
    [12-31-2018 13:33:29.0472] [2] Used domain controller DC03.sztlyy.net to read object CN=Delegated Setup1,OU=Microsoft Exchange Security Groups,DC=sztlyy,DC=net.
    [12-31-2018 13:33:29.0472] [2] Used domain controller DC03.sztlyy.net to read object CN=Delegated Setup1,OU=Microsoft Exchange Security Groups,DC=sztlyy,DC=net.
    [12-31-2018 13:33:29.0483] [2] Used domain controller DC03.sztlyy.net to read object DC=sztlyy,DC=net.
    [12-31-2018 13:33:29.0568] [2] Used domain controller DC03.sztlyy.net to read object CN=AdminSDHolder,CN=System,DC=sztlyy,DC=net.
    [12-31-2018 13:33:29.0736] [2] Can't remove the access control entry on the object "DC=sztlyy,DC=net" for attribute "ExtendedRight (ObjectType: ab721a53-1e2f-11d0-9819-00aa0040529b)" because the ACE isn't present.
    [12-31-2018 13:33:29.0740] [2] Can't remove the access control entry on the object "DC=sztlyy,DC=net" for attribute "CreateChild, DeleteChild (ObjectType: bf967aba-0de6-11d0-a285-00aa003049e2)" because the ACE isn't present.
    [12-31-2018 13:33:29.0744] [2] Can't remove the access control entry on the object "DC=sztlyy,DC=net" for attribute "DeleteChild (ObjectType: bf967aba-0de6-11d0-a285-00aa003049e2)" because the ACE isn't present.
    [12-31-2018 13:33:29.0746] [2] Can't remove the access control entry on the object "DC=sztlyy,DC=net" for attribute "CreateChild, DeleteChild (ObjectType: 4828cc14-1437-45bc-9b07-ad6f015e5f28)" because the ACE isn't present.
    [12-31-2018 13:33:29.0747] [2] Can't remove the access control entry on the object "DC=sztlyy,DC=net" for attribute "DeleteChild (ObjectType: 4828cc14-1437-45bc-9b07-ad6f015e5f28)" because the ACE isn't present.
    [12-31-2018 13:33:29.0749] [2] Can't remove the access control entry on the object "DC=sztlyy,DC=net" for attribute "CreateChild, DeleteChild (ObjectType: bf967a9c-0de6-11d0-a285-00aa003049e2)" because the ACE isn't present.
    [12-31-2018 13:33:29.0751] [2] Can't remove the access control entry on the object "DC=sztlyy,DC=net" for attribute "DeleteChild (ObjectType: bf967a9c-0de6-11d0-a285-00aa003049e2)" because the ACE isn't present.
    [12-31-2018 13:33:29.0755] [2] Can't remove the access control entry on the object "DC=sztlyy,DC=net" for attribute "CreateChild, DeleteChild (ObjectType: 5cb41ed0-0e4c-11d0-a286-00aa003049e2)" because the ACE isn't present.
    [12-31-2018 13:33:29.0757] [2] Can't remove the access control entry on the object "DC=sztlyy,DC=net" for attribute "DeleteChild (ObjectType: 5cb41ed0-0e4c-11d0-a286-00aa003049e2)" because the ACE isn't present.
    [12-31-2018 13:33:29.0759] [2] Can't remove the access control entry on the object "DC=sztlyy,DC=net" for attribute "WriteProperty (ObjectType: 5fd42471-1262-11d0-a060-00aa006c33ed)" because the ACE isn't present.
    [12-31-2018 13:33:29.0761] [2] Can't remove the access control entry on the object "DC=sztlyy,DC=net" for attribute "WriteProperty (ObjectType: 3e0abfd0-126a-11d0-a060-00aa006c33ed)" because the ACE isn't present.
    [12-31-2018 13:33:29.0762] [2] Can't remove the access control entry on the object "DC=sztlyy,DC=net" for attribute "WriteProperty (ObjectType: bf967a7a-0de6-11d0-a285-00aa003049e2)" because the ACE isn't present.
    [12-31-2018 13:33:29.0766] [2] Can't remove the access control entry on the object "DC=sztlyy,DC=net" for attribute "WriteProperty (ObjectType: bf9679c0-0de6-11d0-a285-00aa003049e2)" because the ACE isn't present.
    [12-31-2018 13:33:29.0767] [2] Can't remove the access control entry on the object "DC=sztlyy,DC=net" for attribute "WriteProperty (ObjectType: 0296c120-40da-11d1-a9c0-0000f80367c1)" because the ACE isn't present.
    [12-31-2018 13:33:29.0769] [2] Can't remove the access control entry on the object "DC=sztlyy,DC=net" for attribute "WriteProperty (ObjectType: bf967a0a-0de6-11d0-a285-00aa003049e2)" because the ACE isn't present.
    [12-31-2018 13:33:29.0771] [2] Can't remove the access control entry on the object "DC=sztlyy,DC=net" for attribute "WriteProperty (ObjectType: bf967a68-0de6-11d0-a285-00aa003049e2)" because the ACE isn't present.
    [12-31-2018 13:33:29.0773] [2] Can't remove the access control entry on the object "DC=sztlyy,DC=net" for account "SZTLYY\Exchange Trusted Subsystem1" because the ACE doesn't exist on the object.
    [12-31-2018 13:33:29.0776] [2] Can't remove the access control entry on the object "DC=sztlyy,DC=net" for account "SZTLYY\Exchange Windows Permissions1" because the ACE doesn't exist on the object.
    [12-31-2018 13:33:29.0778] [2] Can't remove the access control entry on the object "DC=sztlyy,DC=net" for attribute "CreateChild, DeleteChild (ObjectType: bf967aa5-0de6-11d0-a285-00aa003049e2)" because the ACE isn't present.
    [12-31-2018 13:33:29.0781] [2] Can't remove the access control entry on the object "DC=sztlyy,DC=net" for attribute "DeleteChild (ObjectType: bf967aa5-0de6-11d0-a285-00aa003049e2)" because the ACE isn't present.
    [12-31-2018 13:33:29.0783] [2] Can't remove the access control entry on the object "DC=sztlyy,DC=net" for attribute "CreateChild, DeleteChild (ObjectType: bf967a86-0de6-11d0-a285-00aa003049e2)" because the ACE isn't present.
    [12-31-2018 13:33:29.0785] [2] Can't remove the access control entry on the object "DC=sztlyy,DC=net" for attribute "DeleteChild (ObjectType: bf967a86-0de6-11d0-a285-00aa003049e2)" because the ACE isn't present.
    [12-31-2018 13:33:29.0787] [2] Can't remove the access control entry on the object "DC=sztlyy,DC=net" for account "SZTLYY\Exchange Windows Permissions1" because the ACE doesn't exist on the object.
    [12-31-2018 13:33:29.0787] [2] Used domain controller DC03.sztlyy.net to write object DC=sztlyy,DC=net.
    [12-31-2018 13:33:29.0874] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1825; Allow; ReadProperty; ContainerInheritAll; 1f298a89-de98-47b8-b5cd-572ad53d267e.
    [12-31-2018 13:33:29.0934] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1825; Allow; ReadProperty; ContainerInheritAll; b1b3a417-ec55-4191-b327-b72e33e38af2.
    [12-31-2018 13:33:29.0995] [2] The appropriate access control entry is already present on the object "DC=sztlyy,DC=net" for account "NT AUTHORITY\Authenticated Users".
    [12-31-2018 13:33:29.0998] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1825; Allow; ReadProperty; ContainerInheritAll; 5fd424a1-1262-11d0-a060-00aa006c33ed.
    [12-31-2018 13:33:30.0059] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1825; Allow; ReadProperty; ContainerInheritAll; bf967a68-0de6-11d0-a285-00aa003049e2.
    [12-31-2018 13:33:30.0120] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1825; Allow; ReadProperty; ContainerInheritAll; 9a7ad945-ca53-11d1-bbd0-0080c76670c0.
    [12-31-2018 13:33:30.0182] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1825; Allow; WriteProperty; ContainerInheritAll; 9a9a021e-4a5b-11d1-a9c3-0000f80367c1.
    [12-31-2018 13:33:30.0247] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1825; Allow; WriteProperty; ContainerInheritAll; 275b2f54-982d-4dcd-b0ad-e53501445efb.
    [12-31-2018 13:33:30.0308] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1825; Allow; WriteProperty; ContainerInheritAll; f0f8ff9a-1191-11d0-a060-00aa006c33ed.
    [12-31-2018 13:33:30.0371] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1825; Allow; WriteProperty; ContainerInheritAll; bf967a7f-0de6-11d0-a285-00aa003049e2.
    [12-31-2018 13:33:30.0432] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1825; Allow; WriteProperty; ContainerInheritAll; 3263e3b8-fd6b-4c60-87f2-34bdaa9d69eb.
    [12-31-2018 13:33:30.0494] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1825; Allow; WriteProperty; ContainerInheritAll; 2cc06e9d-6f7e-426a-8825-0215de176e11.
    [12-31-2018 13:33:30.0558] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1825; Allow; WriteProperty; ContainerInheritAll; 5430e777-c3ea-4024-902e-dde192204669.
    [12-31-2018 13:33:30.0620] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1825; Allow; WriteProperty; ContainerInheritAll; 934de926-b09e-11d2-aa06-00c04f8eedd8.
    [12-31-2018 13:33:30.0684] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1825; Allow; WriteProperty; ContainerInheritAll; 5e353847-f36c-48be-a7f7-49685402503c.
    [12-31-2018 13:33:30.0746] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1825; Allow; WriteProperty; ContainerInheritAll; 614aea82-abc6-4dd0-a148-d67a59c72816.
    [12-31-2018 13:33:30.0807] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1825; Allow; WriteProperty; ContainerInheritAll; 7cb4c7d3-8787-42b0-b438-3c5d479ad31e.
    [12-31-2018 13:33:30.0870] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1825; Allow; WriteProperty; ContainerInheritAll; 6f606079-3a82-4c1b-8efb-dcc8c91d26fe.
    [12-31-2018 13:33:30.0934] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1825; Allow; WriteProperty; ContainerInheritAll; 66437984-c3c5-498f-b269-987819ef484b.
    [12-31-2018 13:33:30.0997] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1825; Allow; WriteProperty; ContainerInheritAll; 8d3bca50-1d7e-11d0-a081-00aa006c33ed.
    [12-31-2018 13:33:31.0063] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1811; Allow; WriteProperty; ContainerInheritAll; bf96791a-0de6-11d0-a285-00aa003049e2.
    [12-31-2018 13:33:31.0126] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1826; Allow; WriteProperty; ContainerInheritAll; bf96791a-0de6-11d0-a285-00aa003049e2.
    [12-31-2018 13:33:31.0191] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1811; Allow; WriteProperty; ContainerInheritAll; bf967953-0de6-11d0-a285-00aa003049e2.
    [12-31-2018 13:33:31.0253] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1826; Allow; WriteProperty; ContainerInheritAll; bf967953-0de6-11d0-a285-00aa003049e2.
    [12-31-2018 13:33:31.0315] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1811; Allow; WriteProperty; ContainerInheritAll; 28630ebc-41d5-11d1-a9c1-0000f80367c1.
    [12-31-2018 13:33:31.0381] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1826; Allow; WriteProperty; ContainerInheritAll; 28630ebc-41d5-11d1-a9c1-0000f80367c1.
    [12-31-2018 13:33:31.0444] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1811; Allow; WriteProperty; ContainerInheritAll; bf967961-0de6-11d0-a285-00aa003049e2.
    [12-31-2018 13:33:31.0505] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1826; Allow; WriteProperty; ContainerInheritAll; bf967961-0de6-11d0-a285-00aa003049e2.
    [12-31-2018 13:33:31.0570] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1811; Allow; WriteProperty; ContainerInheritAll; bf967a06-0de6-11d0-a285-00aa003049e2.
    [12-31-2018 13:33:31.0634] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1826; Allow; WriteProperty; ContainerInheritAll; bf967a06-0de6-11d0-a285-00aa003049e2.
    [12-31-2018 13:33:31.0698] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1811; Allow; WriteProperty; ContainerInheritAll; 3e74f60e-3e73-11d1-a9c0-0000f80367c1.
    [12-31-2018 13:33:31.0765] [2] Adding the access control entry on the object DC=sztlyy,DC=net: S-1-5-21-2881969261-867877157-2118113891-1826; Allow; WriteProperty; ContainerInheritAll; 3e74f60e-3e73-11d1-a9c0-0000f80367c1.
    [12-31-2018 13:33:31.0779] [2] [ERROR] 访问控制列表的长度超过了允许的最大值。
    [12-31-2018 13:33:31.0780] [2] [WARNING] An unexpected error has occurred and a Watson dump is being generated: 访问控制列表的长度超过了允许的最大值。

     



     

    ExchangeSetupLogs.zip

  6. Hello, I would like to ask how to install the system on multiple hard disks. There are script files to share. When there are multiple hard disks in my computer, the deployment system should be installed on the disk number partition where the original system is specified. Is there any solution?

     

     

    你好,请问 在多个硬盘上 安装系统 可有脚本文件分享啊,  当我电脑存在多个硬盘时候,     部署系统要安装在原来系统指定所在的磁盘编号分区上,有什么办法解决吗

  7.  

    The sccm deployment system is automatically deployed to partitions that already have systems.
      I have some computers with multiple hard disks. Suppose the environment has three hard disks in the computer. According to the sata1 sata2 sata3 arrangement, the system has the first partition system on the sata1 disk, and some of the first partitions on the sata2 disk. Some systems are in the system. First partition on sata3 disk
    Then through the sccm deployment automatically determine the deployment to the sata1 disk or sata2 disk or sata3 on the first partition of the system, how to do it?

    The OSDDetectedWinDir variable does not seem to take effect. How do I set this task sequence parameter to the deployment system to automatically determine which disk partition the system is in, and install it in the corresponding partition.

     

    sccm 部署系统自动部署到 已经有系统的分区上问题
     我有些电脑 多个硬盘,假设环境中电脑硬件 3个硬盘 按sata1 sata2 sata3  排列方式, 系统有的在sata1磁盘上第一个分区系统,有的在sata2磁盘上第一个分区,系统有的在sata3磁盘上第一个分区
    那么要通过sccm部署  自动判断部署到sata1磁盘或sata2磁盘或sata3所在系统的第一分区上,改如何操作做呢?

    OSDDetectedWinDir变量貌似不能生效,请问如何设置这个任务序列参数达到部署系统自动判断系统在哪个磁盘分区,就安装在对应的分区。

    222.jpg

    1111.jpg

  8. 2 hours ago, anyweb said:

    它没有与USMT国家移民点交谈,是否配置?

     

    <![LOG [错误。状态码500返回] LOG]!> <time =“07:22:00.631-480”date =“05-21-2018”component =“OSDSMPClient”context =“”type =“0”thread =“4276”file =“libsmsmessaging.cpp:9551”>
    <![LOG [Received [1164 byte response。] LOG]!> <time =“07:22:00.631-480”date =“05-21-2018”component =“OSDSMPClient” context =“”type =“0”thread =“4276”file =“smpclient.cpp:2376”>
    <![LOG [pReply!= NULL,HRESULT = 80004005(e:\ nts_sccm_release \ sms \ client \ osdeployment \ osdsmpclient \ smpclient.cpp,2391)] LOG]!> <time =“07:22:00.631-480”date =“05-21-2018”component =“OSDSMPClient”context =“”type =“0”thread =“ 4276“file =”

    <![LOG [ClientRequestToSMP :: ClientRootShareRequestToSMP失败。error =(0x80004005)。] LOG]!> <time =“07:22:00.631-480”date =“05-21-2018”component =“OSDSMPClient”context =“”type =“3”thread =“4276 “file =”smpclient.cpp:2442“>
    <![LOG [ExecuteRootShareInfoRequest(sRootShareList),HRESULT = 80004005(e:\ nts_sccm_release \ sms \ client \ osdeployment \ osdsmpclient \ smpclient.cpp,1717)] LOG]!> time =“07:22:00.631-480”date =“05-21-2018”component =“OSDSMPClient”context =“”type =“0”thread =“4276”file =“smpclient.cpp:1717”>
    < ![LOG [ClientRequestToSMP :: DoRequest失败。错误=(0x80004005)。

     

     

    Hello, state migration point configuration, ah, Is dns problem?

    2 hours ago, anyweb said:

     

     

     

  9. 测试环境,测试环境

    Win2016

    SCCM1706  

    ADK1709

    测试客户端系统,测试客户端系统

    Win10和Win7的

     

    Usmt捕获用户状态失败0x00004005,请解决,谢谢

    出现捕获用户状态失败
    这怎么一回事?

    无法捕获用户状态,因此无法捕获用户状态
    ,发生了什么?

     

    smsts.log

    1112.png

    5555.png

    3334444.png

    55444.png

    20180522_100750.jpg

     

     

    已解决,通过网络保存用户状态迁移,不能用中文文件夹,改成英文 就可以正常通过网络捕获状态转移了。

    Has been resolved, through the network to save the user state migration, can not use the Chinese folder, change to English can be normally transferred through the network capture state.

  10. SCCM 1802 版本  

    操作系统 Win 2016

    选HTTS通信得话,应用程序目录和WEB服务不能正常

    安装https 443 应用web目录 失败

    日志如下

    SCCM 1802 version

    Operating System Win 2016

    If HTTS communication is selected, the application directory and WEB service cannot be normal.

    Failed to install https 443 application web directory

    The log is as follows

     

    <05/10/18 14:23:40> ====================================================================
    <05/10/18 14:23:40> SMSAWEBSVC Setup Started....
    <05/10/18 14:23:40> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:SCCM SMSAWEBSVC 0
    <05/10/18 14:23:40> Installing Pre Reqs for SMSAWEBSVC
    <05/10/18 14:23:40>         ======== Installing Pre Reqs for Role SMSAWEBSVC ========
    <05/10/18 14:23:40> Found 1 Pre Reqs for Role SMSAWEBSVC 
    <05/10/18 14:23:40> Pre Req SqlNativeClient found.
    <05/10/18 14:23:40> SqlNativeClient already installed (Product Code: {E381D93A-761D-419F-AD91-D770495D33BD}). Would not install again.
    <05/10/18 14:23:40> Pre Req SqlNativeClient is already installed. Skipping it.
    <05/10/18 14:23:40>         ======== Completed Installation of Pre Reqs for Role SMSAWEBSVC ========
    <05/10/18 14:23:40> Installing the SMSAWEBSVC
    <05/10/18 14:23:40> Passed OS version check.
    <05/10/18 14:23:40> IIS Service is installed.
    <05/10/18 14:23:40> Checking whether IIS ASP.NET component is installed
    <05/10/18 14:23:40> IIS component ASP.NET is installed
    <05/10/18 14:23:40> Checking whether WCF 40 is activated
    <05/10/18 14:23:40>  WCF 40 is activated
    <05/10/18 14:23:40> Checking whether IIS ASP.NET is registered
    <05/10/18 14:23:40>  IIS ASP.NET is registered
    <05/10/18 14:23:40> AWEBSVCNAME="CMApplicationCatalogSvc" SMSSSLSTATE=1 AWEBSVCPATH="D:\Program Files\SMS_CCM" AWEBSVCLOGMAXSIZE=8000000
    <05/10/18 14:23:40> No versions of SMSAWEBSVC are installed.  Installing new SMSAWEBSVC.
    <05/10/18 14:23:40> Enabling MSI logging.  awebsvc.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\awebsvcMSI.log
    <05/10/18 14:23:40> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\awebsvc.msi AWEBSVCNAME="CMApplicationCatalogSvc" SMSSSLSTATE=1 AWEBSVCPATH="D:\Program Files\SMS_CCM" AWEBSVCLOGMAXSIZE=8000000
    <05/10/18 14:23:42> awebsvc.msi exited with return code: 1603
    <05/10/18 14:23:42> Backing up D:\Program Files\Microsoft Configuration Manager\logs\awebsvcMSI.log to D:\Program Files\Microsoft Configuration Manager\logs\awebsvcMSI.log.LastError
    <05/10/18 14:23:42> Fatal MSI Error - awebsvc.msi could not be installed.
    <05/10/18 14:23:42> ~RoleSetup().
     

    11.png

    222.png

    3.png

  11. SCCM1606 Upgrade prompt to register DRC, 

     

     

    搭建环境:Win2012R2(SCCM)                                     域服务器:Win2012R2(AD1 and AD2)

    Setting up environment: Win2012R2(SCCM)               Domain server:Win2012R2 (AD1 and AD2)

     

     

    远程拆分压缩删除了,再安装 还是一样会出现报错RDC,不知怎么回事了!

    Remote split compression deleted, and then install the same or the error RDC, I do not know how the matter!

     

    困扰很久了,求助各位有知道的吗?

    Troubled for a long time, help you have to know?

    ConfigMgrPrereq.log

    ConfigMgrSetup.log

    sccm2.jpg

    sccm1.jpg

  12. :D OK, 我想到了 用 以前的SCCM2012老版本的捕获映像包 来捕获也可以正常捕获, 因为某些特殊情况下,暂时只有XP支持兼容软件

     

    OK, I thought of the previous version of the SCCM2012 capture image packet capture can also be normal capture, because in some special circumstances, the only XP support compatible software

  13. 6632045231537389885.jpg

     

     

     

     

    SCCM2016-1606 version of the capture XP suggested that this 0x0000007F, before the version can be used SCCM2012, 1606 can not support XP capture, there is no way to solve?

     

     

     

    SCCM2016-1606版本捕获XP提示这个0x0000007F,以前用SCCM2012版本的可以,1606没办法支持XP捕获了吗,有没办法解决?

     

     

     

×
×
  • 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.