So we have 3 domain controllers, the CA is hosted at the first one Win 2012 R2, we do have another one which is Win 2016, is it okay? or the CA host needs to be win 2016 or above?
I didn't see such info from the docs.
Thanks a lot for your comment, this is really helpful, even though I also came across that document earlier.
My next questions are:
We are now running our DC at Windows 2012 R2 version, do we have to upgrade to 2016 or later for the implementation? Our DC has CA (sha256) configured, which was used for SCCM PKI
I watched some steps via YouTube and it seems that we also need to configure our Azure AD tenant ID or something at AAD Connect server? Currently we have our AAD Connect working.
Thanks.
Yes we are using USB-C network adapter for X1 to boot from network. The fact is that this adapter works great with any other laptops, Dell, HP, even thinkpad L380, L390, etc.
We didn't try to boot from USB stick because we got a lot of customized setup via MDT and a clear installation from USB doesn't look fine to us:(
We leave TFTP option in WDS as default, not sure if we need to revise any settings there for this special case?
Thanks a lot for your comments.
Hi @FaeryFu-MSFT,
I'm using Office 365 C2R so the client program is always up to date. it's the device related issue since the account can be used in other PCs without this kind of issue.
Thanks @KyleXu-MSFT, it's fixed by manually removing the permission from admin center, I don't need full access to those shared mailboxes:)
I did follow the links earlier, that was why I asked this question. I followed and neither ps1 or cmd scripts worked for me.
When I used the ps1 script, it showed powershell not detected, even though I've enabled powershell support in WinPE boot images.
Any idea?
Just writing to update you that I found another way to accomplish my aim, following this link:
https://www.winsysadminblog.com/2016/08/setting-the-default-wallpaper-on-a-windows-10-image-deployment-through-mdt/
I had to put the above script in the period of State Restore and it works just fine for me:)
Thanks again for your efforts in this.
That's the point, we wanted to have a default background wallpaper but without preventing users from changing the image.
Users would still able to change the image if they like.
Hi @Garth,
Thanks for your message. I'm not sure if I input the wrong switch trying silent install.
After I removed the switch parameters and allowed users to interact with the installation process, the erro code wss gone.
Hi @ChristyZhang-MSFT,
Thanks for your comment, it's a bit bad that new Outlook didn't give us the option to either Close or Minimize the window with X. Never mind, I got it and thanks for your help all the same.