Hello Team,
Please help to implement windows server 2016 FTP server in our premises we wan to implement with domain integrate ftp when users access the ftp data folder open only domain users with authentication to upload data and download data not to delete the data in ftp only administrator can delete the data . For outsider users access the ftp server with users name and password and upload and download data in ftp not to delete the data in ftp.
Hello team,
please suggest while the join system to domain we are getting the error network path was not found.
this error getting a one subnet ( whenever if we use the dhcp pc join smooth no error getting on this subnet if we are use the static IP we are getting the error ) other sublet pc join and work perfectly static IP as well as DHCP IP .
In our current setup we have a Remote Access Server (Windows Server 2016) which we have configured to authenticate vpn connections to our NPS servers.
What we have noticed is that this configuration is lost every time we reboot the box.
More specifically we have configured a remote radius group within the NPS server of the remote access server and every time we reboot the members of the group are lost. However these members still appear to be active in the direct access wizard although obviously they are not.
This group was generated by the windows direct access wizard but we have also tried creating a new group and populating that with our nps servers.
We would like a technician from microsoft to look into this and try to replicate this config and if possible report this as a bug with MS.
Thanks in advance.
The usual procedure was that we are booting client with PXE boot, then a menu appears with the availlable boot images, after selecting a boot image a menu with the task sequences from MDT appears.
The boot images are loaded into WDS on hour server. I import them in WDS with add bootimage - point to litetouch wds which is in the deployment share, litetouch x64. Give a description and then this is what i see when booting a client into PXE.
Now i have added another deployment share on a NAS and also imported the litetouchx64 that is in the boot folder of that deploymentshare, into WDS with a new name. I thought that both where became visible when booting client into PXE but now i do not get a menu anymore when booting into PXE but the client goes straight to the Task sequences of MDT.
Where can i arrange the the boot menu is visible.
hi,
I am trying to perform in-place upgrade from windows server 2008 R2 Sp1 to windows server 2012 R2 Sp1.
The installer copies its temp/setup files, momentarily says that Setup is Starting, and then unceremoniously quits.
no error nothing, can some one help how to fix this?
Regards, Deepak Sharma
Hi,
Currently we have a KMS server wich is running on a Windows Server 2012.
This KMS server uses the "Windows Srv 2012R2 DataCtr/Std KMS" kms key to activate Windows 7 and 10 - Server 2008 and server 2012. This KMS server also activates Office 2010 which uses "Office2010 KMS, Volume KMS channel".
However we still want to activate the same OSes but now extended with Server 2016.
If I add the following key Windows Srv 2016 DataCtr/Std KMS, will the Office 2010 activation still work?
Kr,
Joeri
Hello Everyone,
We try to deploy Windows 10 x64 Enterprise with UEFI machines.
The WDS Server Plattform is 2012 R2 x64.
Im Playing around with Domainjoin for one Week now and cannot find an answer.
Panther Setuperr.log gives me:
2017-01-18 14:14:47, Error [DJOIN.EXE] Unattended Join: NetJoinDomain failed error code is [5]
2017-01-18 14:14:48, Error [DJOIN.EXE] Unattended Join: Unable to join; gdwError = 0x5
Unattended File is with flags
<settings pass="specialize">
<component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<Identification>
<Credentials>
<Domain>xxx</Domain>
<Username>mdtinstall</Username>
<Password>xxx</Password>
</Credentials>
<JoinDomain>xxx</JoinDomain>
<DebugJoin>true</DebugJoin>
<TimeoutPeriodInMinutes>1</TimeoutPeriodInMinutes>
</Identification>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<TimeZone>W. Europe Standard Time</TimeZone>
<ProductKey>NPPR9-FWDCX-D2C8J-H872K-2YT43</ProductKey>
<ComputerName>%MACHINENAME%</ComputerName>
<RegisteredOrganization>xxx</RegisteredOrganization>
<RegisteredOwner>IT Department</RegisteredOwner>
</component>
</settings>
any suggestions?
hello,
iam a newbie to windows server., just here to learn some concepts.am currently using dell xps 13 2016. and not able to install windows server 2016 as the usb thumb drive is NTFS and is not detected in my BIOS. please give me a way to successfully install using a FAT32 file system as my BIOS is detecting this file system
Hi
We have Domain Controller with windows server 2016 r2 ,
can we install server 2012 as ADC for existing 2016 r2 Domain?
Arvind
Greetings,
We have Windows Server licenses on eOpen (the service center) with keys, however, no option to download as it states it must be downloaded through a separate download center.
Can someone provide the process for doing so please?
Thank you.
Alert from Microsoft Forum
I received an error after attempting to install the latest Cumulative update KB4462928 on a Windows 2016 server 1607 build 14393.477 (no updates applied): "The update is not applicable to your computer" - I want the latest code on this server with least time spent acquiring and applying updates.
I thought the cumulative updates were not progressive like the old service pack but i must be wrong. Do i need to install many updates to run latest code or have i missed something? Where is the documentation about this nonsense?
I really hate the idea of having to install many updates before i have the most recent code. I thought that was behind us.
Thank you
Hello,
I've been tasked with creating a VM that will update java and adobe flash for out 5,000 machines on our school district network. We have been having our Techs go out to machines and manually do it when need be. Anybody have any experience with that.
From what I can tell, Oracle says to get the offline installer and use GPO to push it out, but that's not necessarily what we want to do.
Any responses would be greatly appreciated.
Hi,
we are trying to implement a new network model so that all out test systems, which are currently in a Workgroup (no domain whatsoever) are moved to a domain. In the process we've also set up a WDS server which does the joining to the domain when Windows
is installed. In WDS the PCs are prestaged so that they join the correct OU and have the correct hostname (in the unattend.xml we use %MACHINENAME% for the <ComputerName>).
The problem we are facing is the fact that we are using dual boot on our systems. This works fine for workgroups but as soon as we add the PC to the domain on one OS, the other OS loses the trust relationship. This is because the 2 OSs use the same Computer object in AD.
One solution would be to use different Computer objects in AD which would be fine but then the issue is with prestaging which is bound to the MAC address. So we could only prestage one OS, not both.
Are there any other options that I am missing here?
Thanks,
Mircea
Hello,
I work for a company that is the parent company of many small to mid size businesses. One of the tasks I own is the imaging process. I've recently setup 4 WDS servers for PXE boot at our 4 largest geographic locations with DFS-R. I'm using the MDT to build the reference image the contains only apps that all of our businesses need. From there I have a deployment share and task sequences for each company. Most of our companies are on Windows 10 Pro, except for one. Two of my locations are easy, I have the default gateway set in the MDT database and it knows what OS (reference image) and apps to load. I have two locations that use different hardware models and OSs. For those I have the model set in the MDT database to automatically install the proper OS and apps for the one type of hardware.
The problem I'm trying to solve is how to automate the process for all other hardware types at these two locations. I can't go by default gateway because I need it to be model independent at these locations. I also cannot use model because the other companies use the same models with their individual task sequences. I tried to setup location and model but ended up with a hybrid of both task sequences combined.
Is there a way to say X location and Y model gets Z image, all others at location X use the company specific image?
Any help would be greatly appreciated as this is my first time working with the MDT. I've ready many really good posts and a book from Johan Arwidmark and done a good deal of Googling but those have been my only info sources thus far as I implement this.
And before anyone suggests it, SCCM is not in my near future ;)
Thanks,
Adam
When i installed wds for the first time it started good but when i added images when i tried to boot the clients from pxe they didn't find any server and they booted directly to the hdd i researched the internet but i didn't find the solution i decided to re install wds so i did it but after the configuration it gave an error that couldn't start the service when i checked the log it gave me the following error
Log Name: Applicationand when i tried to start the server it says
Windows Deployment Service Server Could Not Be Started
i tried re installing wds again but it still gaves me the same error
what else can i try I am running Windows Server 2008 R2
Hey guys
When I try to upload the captureimage (Windows 10) i won't find any partition to capture in the wizard. !
I need to be in UEFI mode when PXE booting from WDS, but device comes up in BIOS mode. I am using latest Win 2008 Server R2, fully patched. The board manufacturer insists that the 'Legacy PXE option ROM' is capable of PXE booting into UEFI mode, but I have doubts. For testing, I am using a x64 boot.wim and install.wim extracted from a recent Breckenridge (Windows Storage Server) DVD. How do I know I'm not in UEFI mode?
When booting PXE/WDS:
1. Windows setup is not able to create a partition greater than 2TB on a 3TB drive.
2. In \Windows\Panther\setupact.log I see:
Callback_BootEnvironmentDetect: Detected boot environment: BIOS
When booting from a DVD (I have two choices in BIOS for DVD device, one specifies 'UEFI')
1. Setup creates a full size (2794 GB) GPT drive partition on a 3TB drive.
2. In \Windows\Panther\setupact.log I see:
Callback_BootEnvironmentDetect: Detected boot environment: UEFI
In both PXE and DVD boot, I specify drivers when setup presents the 'install drivers' button, so that the full size 3TB is displayed. Diskpart shows the following after PXE installation:
DISKPART> list disk Disk ### Status Size Free Dyn Gpt -------- ------------- ------- ------- --- --- Disk 0 Online 2794 GB 0 B Disk 1 Online 482 MB 0 B Disk 2 Online 465 GB 0 B DISKPART> select disk 0 Disk 0 is now the selected disk. DISKPART> list part Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 1 Primary 100 MB 1024 KB Partition 2 Primary 60 GB 101 MB Partition 3 Primary 1987 GB 60 GB
Apparently setup did not detect UEFI, and created an non-GPT disk. I thought maybe there was something I had to specify on the WDS side, but found nothing in the GUI. I did find options inwdsutil to display and set a 'default boot program' for specific architectures (my target architecture is x64). WDSUTIL /get-Server /server:SVR.Foo.local /show:Config shows:
Boot Program Policy: Known client PXE prompt policy: OptOut New client PXE prompt policy: OptOut Allow N12 for new clients: Architecture discovery: Enabled Reset boot program: No Default boot programs: x86 - boot\x86\pxeboot.com x64 - boot\x64\pxeboot.com ia64 - boot\ia64\bootmgfw.efi Default N12 boot programs: x86 - boot\x86\pxeboot.n12 x64 - boot\x64\pxeboot.n12 ia64 - boot\ia64\bootmgfw.efi
So I tried changed the default boot program for x64 to (using WDSUTIL /set-Server /BootProgram:boot\x64\bootmgfw.efi Architecture:x64), to look like:
Boot Program Policy: Known client PXE prompt policy: OptOut New client PXE prompt policy: OptOut Allow N12 for new clients: Architecture discovery: Enabled Reset boot program: No Default boot programs: x86 - boot\x86\pxeboot.com x64 - boot\x64\bootmgfw.efi ia64 - boot\ia64\bootmgfw.efi Default N12 boot programs: x86 - boot\x86\pxeboot.n12 x64 - boot\x64\pxeboot.n12 ia64 - boot\ia64\bootmgfw.efi
But I got the same result (Setup cannot configure > 2TB partition, setupact.log shows 'BIOS' boot environment). Am I missing something? Should this work?
Thanks,
Dave