我管理一个 webapp(HP 服务管理器)。升级浏览器(IE、FF)后,我们无法访问 Web 前端。
使用 IE 中的“开发工具”,我看到请求的“结果”是“(中止)”。我期待看到 400 或 500 错误,所以我不确定这意味着什么。
这是什么意思?以及如何解决它?
运行 IE 11、HPSM 9.34
我试图让我的 WSUS 服务器通过代理下载补丁。
代理搞砸了 http 标头。BITS 需要范围标头。
有没有办法让 BITS 不需要范围标头?我无权访问代理,但我需要下载这些补丁。
编辑:
WSUS 在 Server 2012 上
从下面的答案中我尝试了这个(在powershell中,从这里):
Add-Type -Path "$Env:ProgramFiles\Update Services\Api\Microsoft.UpdateServices.Administration.dll"
$Wsus = [Microsoft.UpdateServices.Administration.AdminProxy]::GetUpdateServer("dc1",$False,80)
$db = $wsus.GetDatabaseConfiguration().CreateConnection()
$db.executecommandnoresult('USE SUSDB update tbConfigurationC set BitsDownloadPriorityForeground=1')
这没有用。
我有一个看起来像这样的服务器
服务器1
服务器2
Server3(无法访问)
服务器4
当我尝试打开它时,它显示“当前状态下不允许操作”。我检查了主机和虚拟机本身,没有看到任何挂起或失败的任务。我还能检查什么?
编辑:
我能够浏览到数据存储中的 VM 文件。
怎么了:
我正在尝试将服务器加入域。我能够加入它,重新启动服务器,当我尝试登录时,我得到了错误:
Trust Relationship Between Workstation and Domain Fails
从这篇文章开始,我运行了以下命令:
Test-computersecurechannel -verbose
Test-computersecurechannel -repair -verbose
并得到以下输出:
The secure channel between the local computer and the domain (domain name) is broken.
The attempt to repair the secure channel between the local computer and the domain (domain name) has failed.
我试过的:
我尝试重新加入域。我尝试在 AD 中重置计算机帐户并重新加入域。我尝试重新创建计算机帐户并重新加入域。
我该如何解决?这是 DC 复制问题吗?
我正在运行 Windows 2012。
编辑:
刚刚发现:服务器时间已关闭。CMOS 时钟是时间源(作为 vm)。设置CMOS,但这并没有解决问题...
加入 Windows 域需要哪些端口?我收到一条有趣的消息,服务器可以找到域控制器名称,但无法访问它们。
我在实验室环境中构建了一个 HP 服务管理器实例。我想将旧实例中的数据迁移到这个新实例中。它建立在 MS SQL-Server 数据库之上。
我意识到我可能只是与数据库交互并手动迁移,但我想知道是否有一种简单的“GUI”方法来提取数据进行迁移。有没有人从一个 HP SM 实例迁移到另一个?我该怎么做呢?
我有一个 vmdk 文件和 vmx 文件(以及其他人数据存储中的所有其他文件)复制到我自己的数据存储中。如果我尝试从 vmx 文件进行部署,我会得到一个名为“unknown # (invalid)”的 vm,其中 # 是一个序列号,具体取决于我尝试了多少次。如果我尝试从 vmdk 进行部署,我会得到一个无法启动的虚拟机。
有没有一种简单的方法可以从 VM 文件夹启动并运行 VM?
编辑:当我尝试从 VMX 文件部署时,我得到了这个虚拟机:
而且我无法编辑设置或启动它。
编辑:
我们解决了这个问题。文件是从 VMPlayer 给我们的,硬件版本不兼容。我们降低了硬件版本并导出为 .ova 文件。从那里我们可以导入到 vCenter。
我有一个非常特殊的问题。我无法打开“它有效!” 使用 apache 安装新服务器后的页面。我能够 ssh 到盒子(从网络外部)。Apache 似乎在我的 Centos6.4x86_64 机器上运行得很好。/var/logs/httpd/* 中没有任何用处。我错过了什么?
我现在在网络之外。“服务器”是我家用计算机上运行桥接模式的虚拟机。
公网IP:ABCD
主机:192.168.1.5
虚拟机:192.168.1.8
我有一个将端口 22、80 和 8888 转发到 VM 的 verizon fios 路由器。我可以通过端口 22 进行 ssh,但我无法通过端口 80 浏览到公共 URL。所以 ABCD:22 可以正常工作,但http://ABCD:80不能。
nmap 看它是否在监听:
nmap -sT -O localhost
Starting Nmap 5.51 ( http://nmap.org ) at 2013-10-25 11:10 EDT
Nmap scan report for localhost (127.0.0.1)
Host is up (0.000040s latency).
Other addresses for localhost (not scanned): 127.0.0.1
Not shown: 996 closed ports
PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp
80/tcp open http
3306/tcp open mysql
我尝试在本地(lynx)访问它,它确实有效。那么,问题出在我的端口上吗?
我无法连接到本地网络 (VM) 上的服务器。
我有多个可以连接的服务器。
当我尝试将腻子放入服务器时,我收到消息
Incoming Packet was garbled on decryption
我试过的:
我用谷歌搜索并尝试实施他们的解决方案——强制河豚和 ssh2。还是不行。
我该如何解决?
我正在尝试在 Windows 2012 上安装 SQL Server。在对服务器进行一些更改后,我终于能够启动并运行该向导,但现在无论我如何处理以下错误,它都会失败:
TITLE: SQL Server 安装失败。
SQL Server 安装程序遇到以下错误:
XML 文档中存在错误 (108, 148)..
如需帮助,请单击: http: //go.microsoft.com/fwlink ?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&EvtType=0x066FCAFD%25400x5539C151
LinkID: 20476
Product Name: Microsoft SQL Server
Message Source setup.rll
Message ID: 50000
EvtType: 0x066FCAFD%400x5539C151
我试过的:
CL 安装的结果:
错误结果:-2147467259 结果设施代码:0 结果错误代码:16389
请查看 summary.txt 日志以获取更多详细信息
Verbose CL 安装显示:
Sco: File 'C:\SQL Install\1033_ENU_LP\x64\setup\x64\sql_bids_loc.msi' does not exist
Sco: File 'C:\SQL Install\1033_ENU_LP\x64\setup\x64\sql_bids_loc.msi' does not exist
Package ID sql_bids_loc_Cpu64_1033: NotInstalled
Sco: File 'C:\SQL Install\1036_FRA_LP\x64\setup\x64\sql_bids_loc.msi' does not exist
Sco: File 'C:\SQL Install\1036_FRA_LP\x64\setup\x64\sql_bids_loc.msi' does not exist
Package ID sql_bids_loc_Cpu64_1036: NotInstalled
Sco: File 'C:\SQL Install\1040_ITA_LP\x64\setup\x64\sql_bids_loc.msi' does not exist
Sco: File 'C:\SQL Install\1040_ITA_LP\x64\setup\x64\sql_bids_loc.msi' does not exist
Package ID sql_bids_loc_Cpu64_1040: NotInstalled
Sco: File 'C:\SQL Install\1041_JPN_LP\x64\setup\x64\sql_bids_loc.msi' does not exist
Sco: File 'C:\SQL Install\1041_JPN_LP\x64\setup\x64\sql_bids_loc.msi' does not exist
Package ID sql_bids_loc_Cpu64_1041: NotInstalled
Sco: File 'C:\SQL Install\1042_KOR_LP\x64\setup\x64\sql_bids_loc.msi' does not exist
Sco: File 'C:\SQL Install\1042_KOR_LP\x64\setup\x64\sql_bids_loc.msi' does not exist
Package ID sql_bids_loc_Cpu64_1042: NotInstalled
Sco: File 'C:\SQL Install\1046_PTB_LP\x64\setup\x64\sql_bids_loc.msi' does not exist
Sco: File 'C:\SQL Install\1046_PTB_LP\x64\setup\x64\sql_bids_loc.msi' does not exist
Package ID sql_bids_loc_Cpu64_1046: NotInstalled
Sco: File 'C:\SQL Install\1049_RUS_LP\x64\setup\x64\sql_bids_loc.msi' does not exist
Sco: File 'C:\SQL Install\1049_RUS_LP\x64\setup\x64\sql_bids_loc.msi' does not exist
Package ID sql_bids_loc_Cpu64_1049: NotInstalled
Sco: File 'C:\SQL Install\2052_CHS_LP\x64\setup\x64\sql_bids_loc.msi' does not exist
Sco: File 'C:\SQL Install\2052_CHS_LP\x64\setup\x64\sql_bids_loc.msi' does not exist
Package ID sql_bids_loc_Cpu64_2052: NotInstalled
Sco: File 'C:\SQL Install\3082_ESN_LP\x64\setup\x64\sql_bids_loc.msi' does not exist
Sco: File 'C:\SQL Install\3082_ESN_LP\x64\setup\x64\sql_bids_loc.msi' does not exist
Package ID sql_bids_loc_Cpu64_3082: NotInstalled
Sco: File 'C:\SQL Install\1053_SVE_LP\x64\setup\x64\sql_bids_loc.msi' does not exist
Sco: File 'C:\SQL Install\1053_SVE_LP\x64\setup\x64\sql_bids_loc.msi' does not exist
Package ID sql_bids_loc_Cpu64_1053: NotInstalled
Sco: File 'C:\SQL Install\x64\setup\x64\sql_ssms.msi' does not exist
Sco: File 'C:\SQL Install\x64\setup\x64\sql_ssms.msi' does not exist
Package ID sql_ssms_Cpu64: NotInstalled
Sco: File 'C:\SQL Install\1028_CHT_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist
Sco: File 'C:\SQL Install\1028_CHT_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist
Package ID sql_ssms_loc_Cpu64_1028: NotInstalled
Sco: File 'C:\SQL Install\1031_DEU_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist
Sco: File 'C:\SQL Install\1031_DEU_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist
Package ID sql_ssms_loc_Cpu64_1031: NotInstalled
Sco: File 'C:\SQL Install\1033_ENU_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist
Sco: File 'C:\SQL Install\1033_ENU_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist
Package ID sql_ssms_loc_Cpu64_1033: NotInstalled
Sco: File 'C:\SQL Install\1036_FRA_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist
Sco: File 'C:\SQL Install\1036_FRA_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist
Package ID sql_ssms_loc_Cpu64_1036: NotInstalled
Sco: File 'C:\SQL Install\1040_ITA_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist
Sco: File 'C:\SQL Install\1040_ITA_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist
Package ID sql_ssms_loc_Cpu64_1040: NotInstalled
Sco: File 'C:\SQL Install\1041_JPN_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist
Sco: File 'C:\SQL Install\1041_JPN_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist
Package ID sql_ssms_loc_Cpu64_1041: NotInstalled
Sco: File 'C:\SQL Install\1042_KOR_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist
Sco: File 'C:\SQL Install\1042_KOR_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist
Package ID sql_ssms_loc_Cpu64_1042: NotInstalled
Sco: File 'C:\SQL Install\1046_PTB_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist
Sco: File 'C:\SQL Install\1046_PTB_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist
Package ID sql_ssms_loc_Cpu64_1046: NotInstalled
Sco: File 'C:\SQL Install\1049_RUS_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist
Sco: File 'C:\SQL Install\1049_RUS_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist
Package ID sql_ssms_loc_Cpu64_1049: NotInstalled
Sco: File 'C:\SQL Install\2052_CHS_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist
Sco: File 'C:\SQL Install\2052_CHS_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist
Package ID sql_ssms_loc_Cpu64_2052: NotInstalled
Sco: File 'C:\SQL Install\3082_ESN_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist
Sco: File 'C:\SQL Install\3082_ESN_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist
Package ID sql_ssms_loc_Cpu64_3082: NotInstalled
Sco: File 'C:\SQL Install\1053_SVE_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist
Sco: File 'C:\SQL Install\1053_SVE_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist
Package ID sql_ssms_loc_Cpu64_1053: NotInstalled
Sco: File 'C:\SQL Install\x64\setup\sql_common_core_msi\x64\sql_common_core.msi' does not e
Sco: File 'C:\SQL Install\x64\setup\sql_common_core_msi\x64\sql_common_core.msi' does not e
Package ID sql_common_core_Cpu64: NotInstalled
Sco: File 'C:\SQL Install\1028_CHT_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core
Sco: File 'C:\SQL Install\1028_CHT_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core
Package ID sql_common_core_loc_Cpu64_1028: NotInstalled
Sco: File 'C:\SQL Install\1031_DEU_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core
Sco: File 'C:\SQL Install\1031_DEU_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core
Package ID sql_common_core_loc_Cpu64_1031: NotInstalled
Sco: File 'C:\SQL Install\1033_ENU_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core
Sco: File 'C:\SQL Install\1033_ENU_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core
Package ID sql_common_core_loc_Cpu64_1033: NotInstalled
Sco: File 'C:\SQL Install\1036_FRA_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core
Sco: File 'C:\SQL Install\1036_FRA_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core
Package ID sql_common_core_loc_Cpu64_1036: NotInstalled
Sco: File 'C:\SQL Install\1040_ITA_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core
Sco: File 'C:\SQL Install\1040_ITA_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core
Package ID sql_common_core_loc_Cpu64_1040: NotInstalled
Sco: File 'C:\SQL Install\1041_JPN_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core
Sco: File 'C:\SQL Install\1041_JPN_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core
Package ID sql_common_core_loc_Cpu64_1041: NotInstalled
Sco: File 'C:\SQL Install\1042_KOR_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core
Sco: File 'C:\SQL Install\1042_KOR_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core
Package ID sql_common_core_loc_Cpu64_1042: NotInstalled
Sco: File 'C:\SQL Install\1046_PTB_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core
Sco: File 'C:\SQL Install\1046_PTB_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core
Package ID sql_common_core_loc_Cpu64_1046: NotInstalled
Sco: File 'C:\SQL Install\1049_RUS_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core
Sco: File 'C:\SQL Install\1049_RUS_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core
Package ID sql_common_core_loc_Cpu64_1049: NotInstalled
Sco: File 'C:\SQL Install\2052_CHS_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core
Sco: File 'C:\SQL Install\2052_CHS_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core
Package ID sql_common_core_loc_Cpu64_2052: NotInstalled
Sco: File 'C:\SQL Install\3082_ESN_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core
Sco: File 'C:\SQL Install\3082_ESN_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core
Package ID sql_common_core_loc_Cpu64_3082: NotInstalled
Sco: File 'C:\SQL Install\1053_SVE_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core
Sco: File 'C:\SQL Install\1053_SVE_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core
Package ID sql_common_core_loc_Cpu64_1053: NotInstalled
Sco: File 'C:\Users\Administrator\AppData\Local\Temp\2\SQL Server 2012\Setup\1033_ENU_LP\x6
lSupport.msi' does not exist
Sco: File 'C:\Users\Administrator\AppData\Local\Temp\2\SQL Server 2012\Setup\1033_ENU_LP\x6
lSupport.msi' does not exist
Package ID SqlSupport_Cpu64: NotInstalled
Sco: File 'C:\SQL Install\redist\watson\x86\dw20shared.msi' does not exist
Sco: File 'C:\SQL Install\redist\watson\x86\dw20shared.msi' does not exist
Package ID WatsonX86_Cpu32: NotInstalled
Package ID sqlncli_Cpu64: NotInstalled
Package ID SqlLocalDB_Cpu64: NotInstalled
Package ID SqlLocalDB_CTP3_Cpu64: NotInstalled
Sco: File 'C:\SQL Install\1033_ENU_LP\x64\setup\x86\SSDTStub.msi' does not exist
Sco: File 'C:\SQL Install\1033_ENU_LP\x64\setup\x86\SSDTStub.msi' does not exist
Package ID SSDTStub_Cpu32: NotInstalled
Sco: File 'C:\SQL Install\1033_ENU_LP\x64\setup\x86\SSDTDBSvcExternals.msi' does not exist
Sco: File 'C:\SQL Install\1033_ENU_LP\x64\setup\x86\SSDTDBSvcExternals.msi' does not exist
这是什么意思?
我一直在尝试在 Windows Server 2012 上安装 SQL Server 2012。我不断收到同样的错误:
Managed SQL Server Installer has stopped working
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: scenarioengine.exe
Problem Signature 02: 11.0.3000.0
Problem Signature 03: 5081b97a
Problem Signature 04: Microsoft.SqlServer.Chainer.Setup
Problem Signature 05: 11.0.3000.0
Problem Signature 06: 5081b97a
Problem Signature 07: 18
Problem Signature 08: 0
Problem Signature 09: System.IO.FileLoadException
OS Version: 6.2.9200.2.0.0.272.79
Locale ID: 1033
Additional Information 1: c319
Additional Information 2: c3196e5863e32e0baf269d62f56cbc70
Additional Information 3: 422d
Additional Information 4: 422d950c58f4efd1ef1d8394fee5d263
在最初的谷歌搜索之后,我尝试了以下事情:
错误:
Unhandled Exception: System.IO.FileLoadException: Could not load file or assembl
y 'Microsoft.SqlServer.Configuration.Sco, Version=11.0.0.0, Culture=neutral, Pub
licKeyToken=89845dcd8080cc91' or one of its dependencies. Strong name validation
failed. (Exception from HRESULT: 0x8013141A) ---> System.Security.SecurityExcep
tion: Strong name validation failed. (Exception from HRESULT: 0x8013141A)
--- End of inner exception stack trace ---
at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.CheckForBoo
leanInputSettingExistenceFromCommandLine(ServiceContainer context, String settin
gName)
at Microsoft.SqlServer.Chainer.Setup.Setup.DebugBreak(ServiceContainer contex
t)
at Microsoft.SqlServer.Chainer.Setup.Setup.Main()
应用程序日志有这个:
事件 ID 1026
Application: ScenarioEngine.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileLoadException
Stack:
at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.CheckForBooleanInputSettingExistenceFromCommandLine(Microsoft.SqlServer.Chainer.Infrastructure.ServiceContainer, System.String)
at Microsoft.SqlServer.Chainer.Setup.Setup.DebugBreak(Microsoft.SqlServer.Chainer.Infrastructure.ServiceContainer)
at Microsoft.SqlServer.Chainer.Setup.Setup.Main()
事件 ID 1000:
Faulting application name: ScenarioEngine.exe, version: 11.0.3000.0, time stamp: 0x5081b97a
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16384, time stamp: 0x5010ab2d
Exception code: 0xe0434352
Fault offset: 0x00000000000189cc
Faulting process id: 0x8fc
Faulting application start time: 0x01cecc205109f96e
Faulting application path: D:\x64\ScenarioEngine.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 9174db4d-3813-11e3-93f1-000c29908169
Faulting package full name:
Faulting package-relative application ID:
有什么我想念的想法吗?
无法ping通服务器的一些原因是什么?
我有一个 Windows 2003 框,我可以远程进入但我无法 ping 通它。
我检查过的是:
还有其他想法吗?我是服务器组的一员,网络人员向我保证网络防火墙不会阻止 ICMP 请求或回复。
我正在尝试通过 SSH 连接到负载均衡器上的虚拟 IP。我想连接到这个虚拟主机名,并让它把我连接到其中一个虚拟主机。问题是当我尝试 ssh 到虚拟 IP 时,实际 IP 之一响应(重置我的连接)。
有没有办法配置网络以允许通过 ssh 连接到虚拟主机名并将它连接到其中一台主机?
例如网络:192.168.0.3 -- server-cluster01 - .4 -- server01 - .5 -- server02 - .6 -- 管理
管理的主机文件包含 server-cluster01 的条目。
从管理框:
root@managment~: ssh server-cluster01
从我得到的监控工具
192.168.0.6 -> syn 192.168.0.3
192.168.0.4 -> ack 192.168.0.6
192.168.0.6 -> rst 192.168.0.3
(repeat)
许多应用程序服务器开始在我的域中出错。故障排除导致我错误配置了 NTP。我解决了这个问题,但我不知道这个问题最初是怎么出现的。
我能找到的唯一错误是
System Error: 1097
Source: useenv
System Error: 1058
Source: useenv
System Error: 1030
Source: useenv
System Error: 1000
Source: mmc
我还能如何找出 NTP 开始在我的域上运行的原因?是否有任何故障排除步骤来诊断为什么我的 DC 开始从错误时间的随机时间服务器中提取数据?
编辑:
当前问题实际上仍然存在:两个 2003 DC 未与 PDC(2k8 盒)同步。
w32tm /resync -- The computer did not resync because no time data was available.
在实验室环境中,我试图将 SCCM 服务器 (2007) 配置为我们跨三个不同域的补丁解决方案。
DOMAIN A (domA.sample):
The trusted domain. SCCM01 (Server) is on this network.
DOMAIN B (domB.sample):
One way trust between the two domains. DOMAIN B trusts DOMAIN A, but not the other way around.
DOMAIN C (domC.sample):
No trust between this domain and any other domain.
SCCM 在域 A 上设置并运行。该域上的任何服务器都将收到补丁。我目前正在研究域 B(单向信任)。我无法在我的 SCCM 服务器中添加查找系统。我能够在 ServerA.domB.sample 上手动安装客户端,并且站点代码恢复正确,即使我重新发现站点代码,但不知何故 ServerA 未与 SCCM01 通信。
我试过的:
http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/6f06bbf1-6ff4-4a41-9d42-894c1a6e13ea
http://scexblog.blogspot.com/2010/06/sccm-discover-another-trusted-domain.html
有人有 SCCM 的经验吗?