Hi,
While deploying WDS am facing an error while giving the credentials that "Invalid credentials: The network name cannot found". I don;t know why it happen like that. Kindly please give as solution.
Hi,
While deploying WDS am facing an error while giving the credentials that "Invalid credentials: The network name cannot found". I don;t know why it happen like that. Kindly please give as solution.
I've received an error with using a custom unattend.xml file when testing a Windows 10 image. After checking the setupact file, at the bottom I see the error "[Shell Unattend] TimeZone: Time zone data missing ' ' (0x80070002)", in the "specialize" section.
In my attend file, I have the time zone set to "020" (which should indicate the US central time zone) in the "Specialize" section. Does anyone know what might cause an error like this?
Hi All,
I am currently trying to capture a Windows 7 image using WDS (with MDT).
When running Sysprep I am receiving the following error message on screen -
Here is a link to my error log -
Any help with finding a solution to my challenge will be greatly appreciated.
Kind Regards,
Davo
Hi Team
Facing com + issue
Registry Key: CLSID\{D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}\InProcServer32
Process Name: RunDll32.exe Comsvcs.dll file version: not loaded
how to resolve this issue , solution expected.
Thanks
Saravanakumar
I have a Root CA and Sub-CA installed.
Installing OCSP server for Revocation list for the Sub-CA.
I want to setup the Sub-CA to send CRLs only to the OCSP server and not to ldap.
Thank you for your help...
Hi am working on a new Windows Server 2016 acting as a Domain Controller. I would like to deploy Quick Access 'pins' via Group Policy show that network shares are automatically applied to around 100+ users.
***We are not using drive mappings in this instance and Quick Access pins must be used***
I have been trying to add a 'shortcut' in user policy but can not seem to find a way to get the shortcut to appear in the Quick Access.
Am I missing something or is this not doable?
Dear Experts,
https://technet.microsoft.com/en-us/library/ff793434.aspx
KMS activations are valid for 180 days. To remain activated, KMS client computers must renew their activation by connecting to the KMS host at least once every 180 days. By default, KMS client computers attempt to renew their activation every seven days.
If KMS activation fails , the client will retry every two hours. After a client computer’s activation is renewed, the activation validity interval begins again.
How to change the "Activation Validity Interval" from 180 days to 360 days?
We have Windows Server 2012 and windows Server 2008R2 as our KMS hosts.
Regards
Dev T
Dev T
Hi All,
I am using MDT to capture an image of a computer for later deployment using WDS (towards this end I have utilized these excellent instructions).
From my fully configured client computer (the one that I am about to capture) I issue the command -
net use * \\Server\DeploymentShare$
I then logon with Administrator credentials and am presented with a drive letter (Z in my instances).
I then navigate to Z:\scripts\litetouch.vbs to commence the capture process.
All proceeds fine through MDT/WDS in terms of capturing the image.
However when I boot the client computer up again for the first time I see a message to the effect of 'Could not connect all network drives'.
When inspecting drives using Explorer I see that 'Z' drive is still present, as shown below -
I can right click on the drive and select disconnect. However each time that I reboot I see the drive back inside Explorer.
Attempts to permanently remove the drive using net use /delete have been unsuccessful as shown below -
Finally if I look at the available disks in Computer Management there is no sign of 'Z' drive -
Any help in resolving this issue will be greatly appreciated. Once the issue is fixed I will need to capture another image of the client computer, and hopefully this whole situation will not repeat itself!
Kind Regards,
Davo
when using sysprep /generalize to template my virtual machines, it is not resetting the administrator password, it is leaving it set to what it was originally.
syspreop log shows " [shsetup] CleanupAdministratorPassword: NetUserSetInfo(1003) failed (0x800708c5) [gle=0x000003e5]"
I have already followed the suggestions here: http://social.technet.microsoft.com/Forums/en-US/winserversetup/thread/fb5dea3a-3e36-4c47-a22d-12463f5c203c/
but they did not help.
I have done several clean windows installations with the same issue.
Snake
As far as I know, the following are facts regarding the Administrator password on Windows 2008 R2:
- By default the Administrator account is enabled and the password is blank, but you are forced to set a password at first logon after Windows installation
- Sysprep is supposed to set the Administrator password to blank, unless one is indicated in the unattend file.
On my 2008 R2 images I want to be prompted to set the Administrator password after the image is deployed (and after sysprep has been run on the source machine), but for some reason this is not happening. Instead it just comes up with a logon screen and expects the password that was used on the source machine.
I just want the same behavior as when 2008 R2 is installed from media, which is for the Administrator account to have a blank password, but where I am forced to set one at first boot. I have tried setting the password to blank on the source machine before running sysprep, but then it just automatically logs on the Administrator on the first boot, which I don't want.
What setting can I look for that may be causing this? On a previous image which I created using the same unattend file, this worked as I wanted it to, thus the reason I believe it's a setting on my source machine.
Thanks.
I am trying to do in-place upgrades of two Windows Server 2012 R2 machines to Server 2016 RTM, with the setup tool started from Windows, and I want to keep settings and apps. Setup stops at a certain point with the following message:
Windows Server 2016 installation has failed.
Checking the error log, I can find the following:
CMountWIM::DoExecute: Failed to mount WIM file C:\$WINDOWS.~BT\Sources\SafeOS\winre.wim. Error 0x80070522[gle=0x00000522]
It is the same on both machines.
Any ideas?
I'm really just hoping to save fellow techs some work here. I had no idea what was going on and found very little information on the search engines to guide me to resolution. Here's the short story:
In preparation for increasing volume of Windows 8 sales, we've finally been pushed to the Microsoft approved method of deployment. Our previous imaging solution hasn't seen an upgrade in years. So, I've procured and installed a new Windows Server 2012 server (specifics are unnecessary since none of my trouble was hardware related). After installing Windows Server 2012 Standard (with Active Directory, DHS, DHCP, File and WDS roles), i found that while we could PXE boot BIOS systems, we could not PXE boot UEFI capable systems. We always received a PXE-E16 error (No offeres were received) at the client.
I set various DHCP options, changed NIC drivers, checked DHCP and WDS logs, installed Network Monitor to trace packets, deleted DHCP options, checked DNS, etc.
I finally changed the entire set of server hardware (we'd ordered a second system for backup). No change. Still no offers received while booting a UEFI compliant system which PXE booted BIOS mode perfectly.
I've tried three different UEFI capable client systems, two based on the Asus P9X79 WS mainboard, one based on the P8Z77 WS; all boot BIOS normally and fail with the same error in UEFI mode. I can get into it later but i know that these systems will PXE boot UEFI without problem.
Thank you!
Dear sir,
My windows server cold not search for new updates please find last update cold not successful I need to install SP 1
Please suggest for the same
Update for Windows Server 2008 R2 x64 Edition (KB2749655)
Installation date: ?09-?12-?2016 13:52
Installation status: Canceled
Error details: Code 8024000B
Update type: Important
Install this update to resolve issues in Windows. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article for more information. After you install this item, you may have to restart your computer.
More information:
http://support.microsoft.com/kb/2749655
Help and Support:
http://support.microsoft.com
I have server 2003 as a DC ,but now i have purchase new server & install windows server 2012 ,how to promote OLD server as ADC & NEW server as a DC
PLEASE EXPLAIN STEP BY STEP
shrikant
We have an issue with a handful of user profiles at our establishment. When you go in to the users profile, it just has a folder named '.V2' instead of the usual; Contacts, Documents, etc, etc. but when you go in to the '.V2' folder, there are all the pre-mentioned folders. Why is it creating this .V2 folder over all the original content?
We have tried deleting these profiles locally on the machines and on the network so it recreates them to but no avail, which is the usual fix, the .V2 folder just returns, thus hampering the students access to their network drives and the programs on the laptops/computers.
Any similar issues? We have the same set up at our federations other establishment but we've never encountered this problem.
Thanks.
(Sorry if it's in the incorrect area, I'd just clicked submit a question on the site)
Hi,
I have configured WDS and it works well with the exception of any Office apps failing to load. We get "The application can't start because AppVIsvSubsystems32.dll is missing from your computer"
Office Online repair usually fixes the issue but then when we sysprep it again, load it unto wds and inject the monthly patches, we get the same error again.
Can anyone help or have seen this before?
Dear All,
We are running Windows Server 2008 R2 for our HR web server. Currently, we are changing the URL from HTTP to HTTPS. Some users are still accessing as HTTP, which cause issue as they suddenly are not able to access. I am thinking of doing redirection, so when they are accessing the HTTP://xxxxx, it will automatically redirected to HTTPS://xxxxxxx
Is there anyway from IIS that we could do this? I check from our Public DNS and I don't have any way of doing this.
Thanks
Regards,
H