Jump to content


dj3094

Established Members
  • Posts

    42
  • Joined

  • Last visited

Recent Profile Visitors

1795 profile views

dj3094's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hello Experts, I ran the report "Clients incapable of Https communication", I have seceral clients that are incapable, when I check the cert they are not expired. ALso the report is missing lot of machines. Is there any cycle or something I can run on a machine to change last report date? Any suggestions to make my clients capable Thanks in advance DJ
  2. there are no error messages, but I see many warningsMP has discarded a report when processing the relay: corruption or invalid user definitionPossible cause
  3. hello all,under component status, I see SMS_MP_CONTROL_MANAGER STATUS CRITICAL. what steps do i need to perform to clear this?RegardsDJ
  4. Thanks for the reply. I was not doing that, but will give it a try
  5. Hello experts, We are trying to enable bitlocker and we have everything setup and it work fine with TPM 2.0. But with TPM 1.2 it fails to activate. We created TS to deploy these using dell command and configure utility all the TS is doing below commands 1) Install HaPIdrivers 2) set bios password 3) enable tpm 4)activate tpm 5)install MBAM client 6)trigger 7)restart it works on TPM 2.0 and fails on 1.2. ALso I tried to activate manually on TPM 1.2 and it fails too below message. Error in Setting the Value.Note: To set TPM - 1. Admin Password must be set , 2. TPM must not be owned and 3. TPM must be deactivated. Anys uggestions? Regards
  6. I added the variable after install on login screen I saw polish language and was happy. but as soon as I tried to login, everything is in english. Any suggestions please
  7. thanks so just add set task sequence variable at start of the TS? and remove the unattend.xml? Also i declared variable in TS and to run if Region value and Launguage value matches. How can I overcome that
  8. Thanks for the reply, How can I hardcode them in unattendxml? just replace osduilanguage to pl-PL <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="oobeSystem"> <component name="Microsoft-Windows-International-Core" processorArchitecture="wow64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <InputLocale>%OSDInputLocale%</InputLocale> <SystemLocale>%OSDSystemLocale%</SystemLocale> <UILanguage>%OSDUILanguage%</UILanguage> <UILanguageFallback>%OSDUILanguageFallback%</UILanguageFallback> <UserLocale>%OSDUserLocale%</UserLocale> </component> </settings> <cpi:offlineImage cpi:source="wim:c:/install.wim#Windows 10 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend> Thanks
  9. Hello Nail, I created task sequence according the post. I am deploying on baremetal. I dont have any HTA. Is there any way i can provide region value and language value. I am deploying only in polish and english. SO i have added only polish. any suggestions? Regards
  10. the below script seems to be working, I will confirm after testing $TSProgressUI = new-object -comobject Microsoft.SMS.TSProgressUI $TSProgressUI.CloseProgressDialog() #connect to Task Sequence environment $tsenv = New-Object -COMObject Microsoft.SMS.TSEnvironment # read variables set in the task sequence $title = $tsenv.Value("title") $message = $tsenv.Value("message") $returncode = $tsenv.Value("returncode") $messagebox = new-object -comobject wscript.shell write-output $messagebox.popup("$title ",100," $message ",0) $returncode thanks
  11. May be i am wrong, I am deploying couple applications in custom TS. When the user run from software center it pops up message to close some applications. but what happens if I deploy it as required, does to run and popup message and wait to press ok or it continues?
×
×
  • 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.