Quantcast
Channel: Setup Deployment forum
Viewing all 2818 articles
Browse latest View live
↧

WDS - captured images won't add

February 5, 2018, 11:31 am
$
0
0

I have captured a Windows 10 sysprep'ed image using two different methods:

1. pxe boot with a capture image on the WDS server: using this method, I'm able to save the image locally to a usb drive, but the option to connect to the wds server never works.  The logon screen will never connect.

2. boot to WinPE and capture the image with DISM to a usb drive.

For both methods, when I attempt to add the image to the server under "Install images", I get an error that says "The Data is Invalid".

I'm having trouble finding where the problem may be.  Any direction for troubleshooting this would be greatly appreciated!

↧
Search

Creating a Workgroup in Windows 10

July 28, 2018, 7:49 pm
$
0
0
How do I create and allow other computers in my home to join a workgroup, and share files across those computers in Windows 10?  I used to be able to recognize other computers in my home and share files with them.  One of the Windows 10 "Upgrades/Patches" eliminated that capability.
↧
↧

Setting up Power Point account

July 29, 2018, 11:13 pm
$
0
0

Everytime I place curser in the box for email address, I am automatically kicked to the next page without setting up PP account.

↧

wds only for specific subnet

July 29, 2018, 11:41 am
$
0
0

hello

we have a windows server wich runs dhcp and wds.
the dhcp has different scopes wireless(10.0.1.0) printers(10.0.2.0) and wds(10.0.5.0)

we get about 20 new pc's and those are going to be in the wds scope when they are connected to a specific port on the network. but how can i make sure that wds only works on the wds scope and not that an employee boots his normal pc it goes to network boot.

the server with dhcp and wds has the ip 10.0.1.218

↧

MSDTC issue: msdtc.exe terminating unexpectedly everytime I run a simple code to try a distributed transaction

July 30, 2018, 7:24 pm
$
0
0

I am trying a very simple distributed transaction on Windows 10 PC, but MSDTC.exe keeps dying every time I run the code.

I am new to MSDTC, so I've googled to how to set it up. I've configured everything for it from giving authorization to Network Service (User) to the folders that are related to MSDTC (dlls involved with it, app running the distributed transaction, etc.), and disabled firewalls. But I still get errors as shown below.

Error messages:
-0x8004D01B: ("XACT_E_TMNOTAVAILABLE", "The transaction manager is not available."),

-0x8004D01D: ("XACT_E_CONNECTION_DENIED", "A request to establish a connection with the transaction manager was denied."),

-from the Event Viewer
The XA Transaction Manager attempted to load the XA resource manager DLL.
The call to LOADLIBRARY for the XA resource manager DLL failed:
DLL=C:\Users\swx\Desktop\dll,
HR=0x8007007e, File=com\complus\dtc\dtc\xatm\src\xarmconn.cpp Line=2503.

I thought maybe you can do msdtc only on Window servers, but that doesn't make sense to me b/c clients should be able to run distributed actions on their PCs as well. I'd love anyone's input and help, because this problem has been frustrating me beyond limits for over a week now. Below is a C# code I am using to test msdtc.

    class Program
    {
        static void Main(string[] args)
        {
            string connstr = "this str works for non-distributed transactions";
            PerformTransaction(connstr);
        }
        private static void PerformTransaction(string connstr)
        {
            bool first_tx_result = false;
            bool second_tx_result = false;
            try
            {
                using (TransactionScope ts = new TransactionScope())
                {
                    using (OleDbConnection con = new OleDbConnection(connstr))
                    {
                        con.Open();
                        using (OleDbCommand cmd = con.CreateCommand())
                        {
                            cmd.CommandType = CommandType.Text;
                            cmd.CommandText = string.Format("INSERT INTO T84073 ( NO, NAME, SAL) VALUES (3000, 'king', 1000)");
                            cmd.ExecuteNonQuery();
                            first_tx_result = cmd.ExecuteNonQuery() == 1;
                        }
                        // throw new Exception("Transaction not working out");

                        using (OleDbCommand cmd = con.CreateCommand())
                        {
                            cmd.CommandType = CommandType.Text;
                            cmd.CommandText = string.Format("INSERT INTO T84073 ( NO, NAME, SAL) VALUES (3000, 'ksdg', 1000)");
                            cmd.ExecuteNonQuery();
                            second_tx_result = cmd.ExecuteNonQuery() == 1;
                        }
                        if (first_tx_result && second_tx_result)
                        {
                            ts.Complete();
                        }
                    }
                }
            }
            catch
            {
                //rolling back is taken care of by transaction scope
            }
        }
    }
}



↧
↧

Repairing a Windows Installation 2012 R2

October 31, 2016, 4:17 pm
$
0
0

Hi,

I have a server which recently applied a batch of updates and it screwed it up, the server doesn't boot and the server recovery environment doesnt have as good repair tools as the client (like system restore for example).

Anyway, the server is a write-off i'll rebuild it, i tried loads of stuff.

I thought with the WIM file format that there was a way i could re-apply that WIM to the disk to restore my system in a non-destructive way (that is, to keep my user settings, configurations, and installed software), is this possible?

in the recovery environment i have used DISM to apply the image to the C drive, but it is now like a basic clean install of windows, it's not joined to the domain, it hasn't kept my local users (yet the profiles are still there under c:\users\), it hasn't kept the computer name or the applications installed (yet such application folders still exist in the c:\program files\ folder).

I am sure there was a way to do some sort of non-destructive repair, it's what some of the repair discs did for vista and windows 7 i am sure by utilizing the dism or imagex and WIM method, but i can't find out how to do that.

Anyone know?

Thanks

Steve

↧

auto activate office multiple machines

July 31, 2018, 12:11 pm
$
0
0

ello,

So i have an windows image that i am goeing to capture tomorrow but i want to know something.

i installed office pro plus 2013 and havent started it yet.

we have an kms key and also an kms license server for office 2013 and windows 10.

if i capture the image and add the device to the domain does office automaticly activates?

is this the correct way?

install office 2013 pro plus but dont start it yet

.follow the link above to enter the kms key.

sysprep and then capture the image?

then office should automaticly activate if i install the image on another machine in the domain?


↧

WDS Event 772 not PXE booting with Server 2016 and Gen 2 Hyper-V VM or Physical PC.

August 1, 2018, 8:14 am
$
0
0

New to using WDS. I'm receiving this error when trying to PxE boot on both VM and physical: 

"PXE Network Boot using IPv4 (ESC to cancel)

Performing DHCP Negotiation.......

  Station IP address is 10.100.1.138

  Server IP address is 10.100.1.20

  NBP filename is boot\x64\wdsmgfw.efi

  NBP filesize is 0 Bytes

PXE-E23: Client received TFTP error from server."

 

WDS and DHCP are on the same server. Options 60, 66, and 67 are set. NetBIOS over TCP/IP is disabled on the WINS tab. WDS is standalone. Active Directory is not being used. This is not on a domain. Simple workgroup homelab. The file wdsmgfw.efi is in the RemoteInstall\Boot\x64 directory. It has a file size of 1MB (1,030 KB).

This is the error in the Event Log: 

 

Event 772 WDSServer: An error occurred while trying to create the UDP endpoint for WDSTFTP provider on interface 10.100.1.20:69. This can happen if the network interface was disabled or changed, or some other application is already using the port. The provider  will not be able to receive requests on this interface. 

I can connect to TFTP via the command line TFTP client and download the wdsmgfw.efi from the WDS share with no issues (\boot\x64\wdsmgfw.efi). If I put the IP address of the server in the TFTP CLI, it won't connect and download, however. I have to put the actual server name (Server01 for example) in order for TFTP to connect and download the file. I then tried editing option 66 from the server IP to the actual server name as it worked in the CLI, but still get the same error.

 

CLI TFTP using server IP Address:

C:\Users\Administrator\Desktop\test>tftp -i 10.100.1.20 get \boot\x64\wdsmgfw.efi
 Connect request failed

CLI TFTP using server name:

C:\Users\Administrator\Desktop\test>TFTP -i Server01 get \boot\x64\wdsmgfw.efi
Transfer successful: 1054616 bytes in 1 second(s), 1054616 bytes/s

I'm officially stumped and this is driving me crazy.

To make things even more confusing, even though I keep receiving this TFTP error, I see this in the event logs of WDS:

Event 4096 Deployment-Services-Diagnostics

The following client booted from PXE: 
Hardware Address: 00-15-5D-01-14-14
IP: 10.100.1.132
Device ID: {9D64189E-5C95-4E89-9113-B7A8B8EA98DC}
ClientArchitecture: 4
Prestaged: false


EDIT:

I created a Gen 1 hyper-v VM to try legacy boot, and I get the following errors:

PXE-T01: File not found PXE-E3B: TFTP error - file not found

↧
Search

WDS, howto add custom or automatic computername option?

April 2, 2007, 6:36 am
$
0
0

In RIS we enabled the option to be able to choose, during the OSChoose screens if we want to use automatic computername generation (or use the pre-staged accounts), or manually enter a computername for this machine. This was the custom.osc file.

Now while using the WDS method, i want to unattend almost everything thus minimizing user interaction. The only thing i can't get to work is this part.

How can i create this scenario of being able to choose from Automatic or manual computernaming using WDS?

Btw. we are deploying a captured/sysprepped Windows XP .WIM file, not Vista!

 

Hope to hear good things Wink

↧
↧

NIC Teaming on Server 2016 delays network availability on Domain Controllers causing problems with Active Directory

January 5, 2018, 1:58 am
$
0
0

I have a physical server (IBM HS22) with 2 NICs.  I freshly installed Windows Server 2016 with AD Directory Services, DNS, DFS, and DHCP server roles.  It's up-to-date with Windows Updates.

The two NICs are teamed using lbfoadmin as switch independent, dynamic, and no standby.

Problem

When the server reboots, many unexpected event log entries are recorded.  All the errors are related to networking problems, or lack of networking.

Examples: DNS server could not bind to IP address, ADWS cannot service directory, DFS Rootxxx failed during initialization, ntpclient cannot find peer, Intersite Messaging failed, etc.

I receive 20-40 errors on each boot.

Notes

  • If I break the team and just use one NIC (it doesn't matter which one), these errors do not occur
  • If the team contains only one NIC, and I disable the other NIC, the problem still exists
  • Changing other team settings such as standby adapter and type doesn't help
  • This problem does not appear on similar hardware using 2012 R2
  • Side note:  The services seem to auto-recover because all the server roles seem to be working

I suspect the teaming layer is adding a delay to networking availability and is causing the services to fail because the network is not ready.

I really want the NICs teamed for fault-tolerance.  Any ideas on how I can fix/workaround this problem?

↧

WDS - Changing the default Remote Installation Folder

December 29, 2008, 11:06 am
$
0
0
Hi All -

I have a production W2K8 Server running WDS and someone kept all the defaults when they installed the product. 

So my question is, what's the easiest way to change the default remote installation path from C:\RemoteInstall to my san drive at F:\RemoteInstall? 

Thanks in advance!

Steven
↧

unable to install vc++2008

August 14, 2018, 6:55 am
$
0
0

Operating system version: Windows 2008 R2 sp1 x64
Existing software: SQL server 2008 (the system is automatically installed when installed. Net framework 3.5)
Problem: unable to install vc++2008
Detailed description:

Prepare to deploy a new set of software, provided you need to install vc++2008.The software installation package includes vc++2008, but the installation failed. Installing vc++2008 alone also failed.Use sxstrace to track the installation process of vc++2008 independent installation package "vcredist_x86.exe". The results are as follows.In addition, vc++ version 2012 above can be installed normally, but is not required by the new software.

=================
开始生成激活上下文。
输入参数:
 Flags = 0
 ProcessorArchitecture = Wow32
 CultureFallBacks = zh-CN;zh-Hans;zh;en-US;en
 ManifestPath = C:\Users\Administrator\Desktop\vcredist_x86.exe
 AssemblyDirectory = C:\Users\Administrator\Desktop\
 Application Config File =
-----------------
信息: 正在解析清单文件 C:\Users\Administrator\Desktop\vcredist_x86.exe。
 信息: 指令清单定义标识是 sfxcab.exe,processorArchitecture="X86",type="win32",version="1.0.0.0"。
信息: 生成激活上下文成功。
结束生成激活上下文。
=================
开始生成激活上下文。
输入参数:
 Flags = 0
 ProcessorArchitecture = Wow32
 CultureFallBacks = zh-CN;zh-Hans;zh;en-US;en
 ManifestPath = d:\7fa4ada4fb75998cc57bfa6d24d428c5\install.exe
 AssemblyDirectory = d:\7fa4ada4fb75998cc57bfa6d24d428c5\
 Application Config File =
-----------------
信息: 正在解析清单文件 d:\7fa4ada4fb75998cc57bfa6d24d428c5\install.exe。
 信息: 指令清单定义标识是 Microsoft.VisualStudio.UIHandler,processorArchitecture="X86",type="win32",version="1.0.0.0"。
 信息: 参考: Microsoft.Windows.Common-Controls,language="*",processorArchitecture="X86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0"
信息: 正在解析参考 Microsoft.Windows.Common-Controls,language="*",processorArchitecture="X86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0"。
 信息: 正在解析 ProcessorArchitecture WOW64 的参考。
  信息: 正在解析区域性 zh-CN 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0_zh-CN_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL 上探测指令清单。
    信息: 未找到区域性 zh-CN 的指令清单。
   信息: 结束程序集探测。
  信息: 正在解析区域性 zh-Hans 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0_zh-Hans_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL 上探测指令清单。
    信息: 未找到区域性 zh-Hans 的指令清单。
   信息: 结束程序集探测。
  信息: 正在解析区域性 zh 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0_zh_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL 上探测指令清单。
    信息: 未找到区域性 zh 的指令清单。
   信息: 结束程序集探测。
  信息: 正在解析区域性 en-US 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0_en-US_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL 上探测指令清单。
    信息: 未找到区域性 en-US 的指令清单。
   信息: 结束程序集探测。
  信息: 正在解析区域性 en 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL 上探测指令清单。
    信息: 未找到区域性 en 的指令清单。
   信息: 结束程序集探测。
  信息: 正在解析区域性 Neutral 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0__6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL 上探测指令清单。
    信息: 未找到区域性 Neutral 的指令清单。
   信息: 结束程序集探测。
 信息: 正在解析 ProcessorArchitecture x86 的参考。
  信息: 正在解析区域性 zh-CN 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0_zh-CN_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL 上探测指令清单。
    信息: 未找到区域性 zh-CN 的指令清单。
   信息: 结束程序集探测。
  信息: 正在解析区域性 zh-Hans 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0_zh-Hans_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL 上探测指令清单。
    信息: 未找到区域性 zh-Hans 的指令清单。
   信息: 结束程序集探测。
  信息: 正在解析区域性 zh 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0_zh_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL 上探测指令清单。
    信息: 未找到区域性 zh 的指令清单。
   信息: 结束程序集探测。
  信息: 正在解析区域性 en-US 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0_en-US_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL 上探测指令清单。
    信息: 未找到区域性 en-US 的指令清单。
   信息: 结束程序集探测。
  信息: 正在解析区域性 en 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL 上探测指令清单。
    信息: 未找到区域性 en 的指令清单。
   信息: 结束程序集探测。
  信息: 正在解析区域性 Neutral 的参考。
   信息: 正在应用绑定策略。
    信息: 自动服务策略重定向的程序集版本。
    信息: 发布策略程序集标识是 Microsoft.Windows.Common-Controls,processorArchitecture="x86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.7601.18837"。
   信息: 开始程序集探测。
    信息: 尝试在 C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_41e855142bd5705d.manifest 上探测指令清单。
    信息: 在 C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_41e855142bd5705d.manifest 上找到指令清单。
   信息: 结束程序集探测。
信息: 正在解析参考 Microsoft.Windows.Common-Controls.mui,language="*",processorArchitecture="x86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.7601.18837"。
 信息: 正在解析 ProcessorArchitecture WOW64 的参考。
  信息: 正在解析区域性 zh-CN 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.mui\6.0.7601.18837_zh-CN_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL 上探测指令清单。
    信息: 未找到区域性 zh-CN 的指令清单。
   信息: 结束程序集探测。
  信息: 正在解析区域性 zh-Hans 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.mui\6.0.7601.18837_zh-Hans_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL 上探测指令清单。
    信息: 未找到区域性 zh-Hans 的指令清单。
   信息: 结束程序集探测。
  信息: 正在解析区域性 zh 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.mui\6.0.7601.18837_zh_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL 上探测指令清单。
    信息: 未找到区域性 zh 的指令清单。
   信息: 结束程序集探测。
  信息: 正在解析区域性 en-US 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.mui\6.0.7601.18837_en-US_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL 上探测指令清单。
    信息: 未找到区域性 en-US 的指令清单。
   信息: 结束程序集探测。
  信息: 正在解析区域性 en 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.mui\6.0.7601.18837_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL 上探测指令清单。
    信息: 未找到区域性 en 的指令清单。
   信息: 结束程序集探测。
 信息: 正在解析 ProcessorArchitecture x86 的参考。
  信息: 正在解析区域性 zh-CN 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.mui\6.0.7601.18837_zh-CN_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL 上探测指令清单。
    信息: 未找到区域性 zh-CN 的指令清单。
   信息: 结束程序集探测。
  信息: 正在解析区域性 zh-Hans 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.mui\6.0.7601.18837_zh-Hans_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL 上探测指令清单。
    信息: 未找到区域性 zh-Hans 的指令清单。
   信息: 结束程序集探测。
  信息: 正在解析区域性 zh 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.mui\6.0.7601.18837_zh_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL 上探测指令清单。
    信息: 未找到区域性 zh 的指令清单。
   信息: 结束程序集探测。
  信息: 正在解析区域性 en-US 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.mui\6.0.7601.18837_en-US_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL 上探测指令清单。
    信息: 未找到区域性 en-US 的指令清单。
   信息: 结束程序集探测。
  信息: 正在解析区域性 en 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.mui\6.0.7601.18837_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL 上探测指令清单。
    信息: 未找到区域性 en 的指令清单。
   信息: 结束程序集探测。
信息: 正在解析清单文件 C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_41e855142bd5705d.manifest。
 信息: 指令清单定义标识是 Microsoft.Windows.Common-Controls,processorArchitecture="x86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.7601.18837"。
 信息: 参考: Microsoft.Windows.Common-Controls.Resources,language="*",processorArchitecture="x86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0"
信息: 正在解析参考 Microsoft.Windows.Common-Controls.Resources,language="*",processorArchitecture="x86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0"。
 信息: 正在解析 ProcessorArchitecture WOW64 的参考。
  信息: 正在解析区域性 zh-CN 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.Resources\6.0.0.0_zh-CN_6595b64144ccf1df\Microsoft.Windows.Common-Controls.Resources.DLL 上探测指令清单。
    信息: 未找到区域性 zh-CN 的指令清单。
   信息: 结束程序集探测。
  信息: 正在解析区域性 zh-Hans 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.Resources\6.0.0.0_zh-Hans_6595b64144ccf1df\Microsoft.Windows.Common-Controls.Resources.DLL 上探测指令清单。
    信息: 未找到区域性 zh-Hans 的指令清单。
   信息: 结束程序集探测。
  信息: 正在解析区域性 zh 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.Resources\6.0.0.0_zh_6595b64144ccf1df\Microsoft.Windows.Common-Controls.Resources.DLL 上探测指令清单。
    信息: 未找到区域性 zh 的指令清单。
   信息: 结束程序集探测。
  信息: 正在解析区域性 en-US 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.Resources\6.0.0.0_en-US_6595b64144ccf1df\Microsoft.Windows.Common-Controls.Resources.DLL 上探测指令清单。
    信息: 未找到区域性 en-US 的指令清单。
   信息: 结束程序集探测。
  信息: 正在解析区域性 en 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.Resources\6.0.0.0_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.Resources.DLL 上探测指令清单。
    信息: 未找到区域性 en 的指令清单。
   信息: 结束程序集探测。
  信息: 正在解析区域性 Neutral 的参考。
   信息: 正在应用绑定策略。
    信息: 未找到发布服务器策略。
    信息: 未找到绑定策略重定向。
   信息: 开始程序集探测。
    信息: 未找到 WinSxS 中的程序集。
    信息: 尝试在 C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.Resources\6.0.0.0__6595b64144ccf1df\Microsoft.Windows.Common-Controls.Resources.DLL 上探测指令清单。
    信息: 未找到区域性 Neutral 的指令清单。
   信息: 结束程序集探测。
 信息: 正在解析 ProcessorArchitecture x86 的参考。
  信息: 正在解析区域性 zh-CN 的参考。
   信息: 正在应用绑定策略。
    信息: 自动服务策略重定向的程序集版本。
    信息: 发布策略程序集标识是 Microsoft.Windows.Common-Controls.Resources,language="zh-CN",processorArchitecture="x86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.7600.16385"。
   信息: 开始程序集探测。
    信息: 尝试在 C:\Windows\WinSxS\manifests\x86_microsoft.windows.c..-controls.resources_6595b64144ccf1df_6.0.7600.16385_zh-cn_b7a33d2d3f47b7fb.manifest 上探测指令清单。
    信息: 在 C:\Windows\WinSxS\manifests\x86_microsoft.windows.c..-controls.resources_6595b64144ccf1df_6.0.7600.16385_zh-cn_b7a33d2d3f47b7fb.manifest 上找到指令清单。
   信息: 结束程序集探测。
信息: 正在解析清单文件 C:\Windows\WinSxS\manifests\x86_microsoft.windows.c..-controls.resources_6595b64144ccf1df_6.0.7600.16385_zh-cn_b7a33d2d3f47b7fb.manifest。
 信息: 指令清单定义标识是 Microsoft.Windows.Common-Controls.Resources,language="zh-CN",processorArchitecture="x86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.7600.16385"。
信息: 生成激活上下文成功。
结束生成激活上下文。

Make the future happen

↧

WDS Monitoring : "Unable to access the monitoring data service"

October 6, 2014, 5:42 pm
$
0
0

Hello,

On MDT 2012, under one of the deployment shares, I am getting the error as below

The details shown are :

Assembly: mscorlib  Assembly Version: 4.0.0.0  File Version: 4.0.30319.34014 built by: FX45W81RTMGDR
Assembly: Microsoft.ManagementConsole  Assembly Version: 3.0.0.0  File Version: 6.3.9600.16384
Assembly: System  Assembly Version: 4.0.0.0  File Version: 4.0.30319.34003 built by: FX45W81RTMGDR
Assembly: MMCFxCommon  Assembly Version: 3.0.0.0  File Version: 6.3.9600.16384
Assembly: System.Configuration  Assembly Version: 4.0.0.0  File Version: 4.0.30319.33440 built by: FX45W81RTMREL
Assembly: System.Xml  Assembly Version: 4.0.0.0  File Version: 4.0.30319.33440 built by: FX45W81RTMREL
Assembly: System.Windows.Forms  Assembly Version: 4.0.0.0  File Version: 4.0.30319.33440 built by: FX45W81RTMREL
Assembly: System.Drawing  Assembly Version: 4.0.0.0  File Version: 4.0.30319.33440 built by: FX45W81RTMREL
Assembly: Microsoft.BDD.Workbench  Assembly Version: 3.0.0.0  File Version: 6.2.5019.0
Assembly: Microsoft.BDD.Core  Assembly Version: 3.0.0.0  File Version: 6.2.5019.0
Assembly: Microsoft.BDD.PSSnapIn  Assembly Version: 3.0.0.0  File Version: 6.2.5019.0
Assembly: System.Management.Automation  Assembly Version: 3.0.0.0  File Version: 6.3.9600.17090
Assembly: System.Core  Assembly Version: 4.0.0.0  File Version: 4.0.30319.33440 built by: FX45W81RTMREL
Assembly: System.Numerics  Assembly Version: 4.0.0.0  File Version: 4.0.30319.33440 built by: FX45W81RTMREL
Assembly: System.DirectoryServices  Assembly Version: 4.0.0.0  File Version: 4.0.30319.33440 built by: FX45W81RTMREL
Assembly: System.Management  Assembly Version: 4.0.0.0  File Version: 4.0.30319.33440 built by: FX45W81RTMREL
Assembly: Microsoft.Management.Infrastructure  Assembly Version: 1.0.0.0  File Version: 6.3.9600.16384
Assembly: Anonymously Hosted DynamicMethods Assembly  Assembly Version: 0.0.0.0
Assembly: Microsoft.PowerShell.Commands.Diagnostics  Assembly Version: 3.0.0.0  File Version: 6.3.9600.16384
Assembly: System.Configuration.Install  Assembly Version: 4.0.0.0  File Version: 4.0.30319.33440 built by: FX45W81RTMREL
Assembly: System.Transactions  Assembly Version: 4.0.0.0  File Version: 4.0.30319.33440 built by: FX45W81RTMREL
Assembly: Microsoft.PowerShell.Commands.Utility  Assembly Version: 3.0.0.0  File Version: 6.3.9600.16384
Assembly: Microsoft.PowerShell.ConsoleHost  Assembly Version: 3.0.0.0  File Version: 6.3.9600.16384
Assembly: Microsoft.PowerShell.Commands.Management  Assembly Version: 3.0.0.0  File Version: 6.3.9600.16384
Assembly: Microsoft.PowerShell.Security  Assembly Version: 3.0.0.0  File Version: 6.3.9600.16384
Assembly: Microsoft.WSMan.Management  Assembly Version: 3.0.0.0  File Version: 6.3.9600.16384
Assembly: System.Data  Assembly Version: 4.0.0.0  File Version: 4.0.30319.33440 built by: FX45W81RTMREL
Assembly: System.Data.Services.Client  Assembly Version: 4.0.0.0  File Version: 4.0.30319.33440 built by: FX45W81RTMREL
Assembly: MMCEx  Assembly Version: 3.0.0.0  File Version: 6.3.9600.16384
Assembly: Microsoft.BDD.ConfigManager  Assembly Version: 3.0.0.0  File Version: 6.2.5019.0
Assembly: System.Xml.Linq  Assembly Version: 4.0.0.0  File Version: 4.0.30319.33440 built by: FX45W81RTMREL
 
System.InvalidOperationException: Unable to access the monitoring data service at http://XXXXXXX:9804/MDTMonitorData.  Make sure the MDT monitoring service is running.

   at Microsoft.BDD.Workbench.Utility.RunPSCommand(String commandString, Dictionary`2 parameters)
   at Microsoft.BDD.Workbench.MonitoringListView.Refresh()

Other deployment shares under the same server are fine. The monitoring tab are configured for ports 9803 for event and 9804 for Data.

Any suggestions?

Regards,

Ramu V Ramanan

↧
↧

dism - The directory could not be completely unmounted - process explorer can't find open processes and unmounting fails

December 15, 2009, 5:26 pm
$
0
0
Hi all,

Installed WAIK on server 2008 R2 64 bit. I'm setting up some boot images, and am having a real hard time getting drivers to integrate into the driver store in the boot images.

What I'm finding is that when adding drivers to the boot image the gui hangs part way through over 50% of the time using Dell 760 or HP NX9420 drivers extracted to pull out the inf files. It's really flakey and will work after a couple of attempts and when the wind is right.

The main problem is that when the process fails the image is left open, so using dism to list mounted images and then umount the open images is the only way to try again.

However, some images won't unmount and the unmount process displays the following:

C:\Windows\system32>dism /get-mountedwiminfo

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Mounted images:

Mount Dir : C:\Users\davros\AppData\Local\Temp\~$WDSMGMT.000
Image File : \\DAVROS.stafflib.flinders.edu.au\REMINST\Boot\x86\Images\boot-(2).
wim
Image Index : 2
Mounted Read/Write : Yes
Status : Invalid

The operation completed successfully.

C:\Windows\system32>dism /unmount-wim /mountdir:C:\Users\davros\AppData\Local\Te
mp\~$WDSMGMT.000 /discard

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image File : \\DAVROS.stafflib.flinders.edu.au\REMINST\Boot\x86\Images\boot-(2).
wim
Image Index : 2
Unmounting image
[==========================100.0%==========================]

Error: 0xc1420117

The directory could not be completely unmounted.  This is usually due to applica
tions that still have files opened within the mount directory.  Close these file
s and unmount again to complete the unmount process.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Using process explorer shows no running processes that have the files open and the dism.log file shows:

2009-12-16 11:49:35, Error                 DISM   DISM WIM Provider: PID=5580 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimimage.cpp:75 - CWimImage::Unmount(hr:0xc1420117)
2009-12-16 11:49:35, Error                 DISM   DISM WIM Provider: PID=5580 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:1068 - CWimManager::InternalOpUnmount(hr:0xc1420117)
2009-12-16 11:49:35, Error                 DISM   DISM WIM Provider: PID=5580 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:2318 - CWimManager::InternalCmdUnmount(hr:0xc1420117)
2009-12-16 11:49:35, Error                 DISM   DISM WIM Provider: PID=5580 Error executing command - CWimManager::InternalExecuteCmd(hr:0xc1420117)
2009-12-16 11:49:35, Error                 DISM   DISM WIM Provider: PID=5580 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:516 - CWimManager::ExecuteCmdLine(hr:0xc1420117)
2009-12-16 11:49:35, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2009-12-16 11:49:35, Info                  DISM   DISM.EXE:
2009-12-16 11:49:35, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2009-12-16 11:49:35, Info                  DISM   DISM.EXE:
2009-12-16 11:49:35, Info                  DISM   DISM Image Session: PID=5580 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2009-12-16 11:49:35, Info                  DISM   DISM Provider Store: PID=5580 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2009-12-16 11:49:35, Info                  DISM   DISM Provider Store: PID=5580 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2009-12-16 11:49:35, Info                  DISM   DISM Provider Store: PID=5580 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2009-12-16 11:49:35, Info                  DISM   DISM Provider Store: PID=5580 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2009-12-16 11:49:35, Info                  DISM   DISM Provider Store: PID=5580 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

Rebooting the server clears the lock, but it's really becoming a joke, as I can create a boot image with the drivers, but then going back into add another driver causes the gui to not respond.

Any suggestions gratefully accepted. - Matt.


↧

WDS RemoteInstall folder relocation question

June 9, 2013, 8:29 pm
$
0
0

Hi Guys,

As the space is running out, I have relocated our RemoteInstall to another Drive.

And before the relocations, there is a WDSServer object with Full Control in both the security settings and share permission settings..

After relocation using the wdsutil -uninitialize and wdsutil -initialize command, the WDSServer in the security settings is missing, and I can't add this object in as the system can't find such object.

Is this matter or how can I add WDSServer to security setting?

Thanks!

Weicong888

↧
Search

Microsoft Deployement Toolkit (MDT) - LOG after Up Deployement Share

August 22, 2018, 2:09 am
$
0
0

Hello,

I would like to know where can I find the logs files after updating the image boot from the DeployementWorkbench in Microsoft Deployement Toolkit (MDT) ?

Unfortunately, the is no shared file log centralization.

I am using MDT 6.3 on Windows Server 2016

Thank you in advance,

Regards.

↧

Use of Child Domain in Active Directory

August 22, 2018, 2:35 pm
$
0
0

Hello,

What is the use of multiple child domain in environment.

Regards,

Shashank

shashank saxena

↧
↧

WDS PXE Uefi not working in AD integrated mode, TFTP to slow

February 11, 2015, 5:27 am
$
0
0

Dear all

1 Physical host: W2k12R2, 1 Hyper-V virtual switch.

1 Hyper-V VM with W2k12R2 DC with DNS, DHCP, WDS.

1 Empty Hyper-V VM Generation 2 UEFI booting from network.

Problem: Error "PXE-E16: No offer received" on the empty Hyper-V VM when trying to Uefi boot from WDS in AD integrated mode.

I verified that it works when WDS is set-up to standalone mode. See also: https://social.technet.microsoft.com/Forums/windowsserver/en-US/ceca6149-bedd-4860-8a7f-a1c83bf99aa4/wds-efi-bios-wont-pxe-boot-into-efi-mode

PS: Switch to standalone mode: On the WDS server: wdsutil /verbose /uninitialize-server /server:<servername>; wdsutil /verbose /progress /initialize-server /server:<servername> /reminst:C:\RmInst

Cause (found by Netmon IP traffic monitoring):

The Client asks for the TFTP Server on UDP port 4011.

The TFTP Server takes more than 8 seconds to reply on port 4011.
This seems to be due to NbtNs (Netbios name search) broadcast queries searching for 1C Domain Controllers.

Solution: ???????

Any help is much appreciated.

Dominique, Zürich, Switzerland.

↧

Windows 2016 Server Issue: IIS Off-loaded, Problems Finding Source Files

August 23, 2018, 5:47 pm
$
0
0

OS: Windows Server 2016 (amd64)
Version: 1607 (OS Build 14393.2430
Location: In Azure

I am experiencing a real quandary, a few weeks back I had inadvertently Off Loaded IIS-WebServerRole using DISM /remove.   When i went to reload it back in however, using the /source: parameter, I experienced a "Source files not found" error.

According to the CBS.LOG,  it is failing to find files for a package called "Microsoft-Windows-TerminalServices-Gateway-Packages~31bf3856ad364e35~amd64~en~US~10.0.14393.0".   The directories/files it is failing to find are:

x86_microsoft-windows-rasmprddm_31bf3856ad364e35_10.0.14393.0_none_6a6c211c2bed7ec7\mprddm.dll
x86_microsoft-windows-unimodem-core-tsp_31bf3856ad364e35_10.0.14393.0_none_7f2fc2222dec35c9\unimdm.tsp
amd64_microsoft-windows-rasserver_31bf3856ad364e35_10.0.14393.0_none_d91da4d27e7f8576\*
wow64_microsoft-windows-rasserver_31bf3856ad364e35_10.0.14393.0_none_e3724f24b2e04771\*
amd64_microsoft-windows-rasmprddm_31bf3856ad364e35_10.0.14393.0_none_c68abc9fe44aeffd\mprddm.dll
amd64_microsoft-windows-unimodem-core-tsp_31bf3856ad364e35_10.0.14393.0_none_db4e5da5e649a6ff\unimdm.tsp


I attempted to create the directories in a temporary folder by looking for new versions of the files, however they did not pass the checksum phase of the DISM.EXE feature install.

I checked a dozen other servers for the same file versions/folders and could not find them.

Does anyone know of a way of obtaining said file versions or possibly tricking the operating system into using a later version of the files?



↧

WDS error - event ID 1284 source BINLSVC

March 18, 2018, 6:46 am
$
0
0

Hello,

I have a problem with role WDS on virtual server (Windows Server 2016 on VMware)
We get an error (Event Viewer): 
Description:"An error occurred while trying to create the directory for the  architecture.Error Information: 0x3"
Event ID 1284
Source BINLSVC

I was looking on official page Microsoft and we found:
https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc726671(v%3dws.10)

I have checked permissions for folder E:\RemoteInstall and "WDSServer" account is set to Full control.

Also I have checked registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\ 
and "WDSServer" node was set Full Control for user "SYSTEM".

Could you help me with this? Please


↧
Viewing all 2818 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>