How To Make Shortcuts to Control Panel Pages in Vista
http://www.dailygeeks.com/howto/how-to-make-shortcuts-to-control-panel-pages-in-vista/
How to open Control Panel Items from Command Line in Vista
http://www.nibbleguru.com/problem/5074-how-open-control-panel-items-command-line-vista
New Vista Syntax for Opening Control Panel Items from the Command-line
http://www.howtogeek.com/howto/windows-vista/new-vista-syntax-for-opening-control-panel-items-from-the-command-line/
Accessibility Options, access.cpl
Add/Remove Programs, appwiz.cpl
Add Hardware Wizard, hdwwiz.cpl
Automatic Updates, wuaucpl.cpl
Bluetooth Properties, bthprops.cpl
Display Properties, desk.cpl
Firewall Properties, firewall.cpl
Game Controllers, joy.cpl
Internet Options, inetcpl.cpl
iSCSI Initiator, iscsicpl.cpl
Java Control Panel, jpicpl32.cpl (java install folder\javacpl.exe)
Licensing Mode, liccpa.cpl
Mouse Properties, main.cpl
Network Connections, ncpa.cpl
Network Setup Wizard, netsetup.cpl
ODBC Properties, odbccp32.cpl
Power Options, powercfg.cpl
Regional and Language Options, intl.cpl
Sound and Audio Devices, mmsys.cpl
Stored Passwords, keymgr.cpl
System Properties, sysdm.cpl
Telephone and Modem Properties, telephon.cpl
Time and Date Settings, timedate.cpl
User Accounts, nusrmgr.cpl
Windows Security Center, wscui.cpl
Wireless Link, irprops.cpl
2009-01-27
借助路由器，实现iAMT的本地管理
借助路由器，实现iAMT的本地管理
我们在开发支持Intel主动管理技术的控制台时，访问管理引擎（ME）提供的Web Service接口有两种方式，一种是通过网络访问，另外一种是本机直接访问。但是本机访问有比较多的限制，大部分iAMT功能接口对本地应用程序来说是不可用的，比如CircuitBreak，AgentPresence，SecurityAdministration等等。那么在没有两台机器的情况下，如何实现在iAMT机器的主机操作系统上就能对iAMT所有特性进行操作呢？
经过笔者的一些简单实验，我们只需要一台普通的路由器就能做得到。比如，一般的ADSL接入设备，无线路由器，或者自己用Linux搭建的网关都行。大概的原理是这样的：给iAMT和Host OS配置不同网段的IP地址，都将网关指向路由器；然后在路由器上设定所需的路由；在Host OS上的应用程序访问iAMT IP地址时，网络包首先被发送到默认网关，也就是路由器，然后路由器根据自身的路由表将网络包路由到iAMT，iAMT的返回结果同样也是先发送到路由器，然后由路由器再将网络包路由回Host OS。如下图所示。
在上图中，我们将一台Intel Core 2 vPro机器（内建iAMT功能）的主机操作系统IP地址配置为192.168.2.10，网关指向192.168.1.1，由于这里网关和主机地址不在同一个网段，只能手动配置静态IP了；将底层的iAMT的IP地址配置为192.168.1.10，网关指向192.168.1.1。
这里的路由器兼做网关（我们使用的普通路由器都是这么用的），LAN口配置的IP地址是192.168.1.1；为了使得路由器能够将iAMT返回的数据包回送给Host OS，我们需要在路由表里面增加一项： Destination：192.168.2.0 Netmask: 255.255.255.0 Gateway: 0.0.0.0 (如果是Windows做路由器, 这里就是192.168.1.1)
另外，如果路由器支持LAN接口配置多个IP地址，那只需要为路由器LAN口再配置一个IP地址：192.168.2.1，上面那条路由就能自动加入到路由表；这时候，Host OS的网关可以设置为192.168.2.1。这样，我们就可以在Host OS上通过直接访问底层iAMT的IP来访问iAMT的功能了。比如，通过IE打开：http://192.168.1.10:16992，就可以见到我们熟悉的iAMT WEBUI的登陆界面了。
我在一台LinkSys的无线路由器，和一台Windows 2003 Server的网关上测试过，上述的方法都可以成功。如果你有兴趣，欢迎一起交流探讨。
经过笔者的一些简单实验，我们只需要一台普通的路由器就能做得到。比如，一般的ADSL接入设备，无线路由器，或者自己用Linux搭建的网关都行。大概的原理是这样的：给iAMT和Host OS配置不同网段的IP地址，都将网关指向路由器；然后在路由器上设定所需的路由；在Host OS上的应用程序访问iAMT IP地址时，网络包首先被发送到默认网关，也就是路由器，然后路由器根据自身的路由表将网络包路由到iAMT，iAMT的返回结果同样也是先发送到路由器，然后由路由器再将网络包路由回Host OS。如下图所示。
在上图中，我们将一台Intel Core 2 vPro机器（内建iAMT功能）的主机操作系统IP地址配置为192.168.2.10，网关指向192.168.1.1，由于这里网关和主机地址不在同一个网段，只能手动配置静态IP了；将底层的iAMT的IP地址配置为192.168.1.10，网关指向192.168.1.1。
这里的路由器兼做网关（我们使用的普通路由器都是这么用的），LAN口配置的IP地址是192.168.1.1；为了使得路由器能够将iAMT返回的数据包回送给Host OS，我们需要在路由表里面增加一项： Destination：192.168.2.0 Netmask: 255.255.255.0 Gateway: 0.0.0.0 (如果是Windows做路由器, 这里就是192.168.1.1)
另外，如果路由器支持LAN接口配置多个IP地址，那只需要为路由器LAN口再配置一个IP地址：192.168.2.1，上面那条路由就能自动加入到路由表；这时候，Host OS的网关可以设置为192.168.2.1。这样，我们就可以在Host OS上通过直接访问底层iAMT的IP来访问iAMT的功能了。比如，通过IE打开：http://192.168.1.10:16992，就可以见到我们熟悉的iAMT WEBUI的登陆界面了。
我在一台LinkSys的无线路由器，和一台Windows 2003 Server的网关上测试过，上述的方法都可以成功。如果你有兴趣，欢迎一起交流探讨。
Out of Band Management简介
http://blogs.technet.com/msdchina/archive/2009/01/08/out-of-band-management-sccm-2007-.aspx
Out of Band Management简介 —— SCCM 2007 Out of Band Management专题系列之一
Out of Band Management正在逐步成为IT管理的主流技术，本专题系列计划就SCCM 2007中Out of Band Management feature做一些介绍和探讨，来帮助读者了解并使用SCCM 2007中的Out of Band Management技术，系列将包括简介，使用，调错等专题文章。
Out of Band Management简介
Out of Band Management是指带外管理技术，是一种不依赖于操作系统就可对目标机器进行管理的技术，目前Intel的AMT（Active Management Technology）和DASH标准（Desktop and mobile Architecture for System Hardware）都提供了Out of Band Management的支持。 在SCCM 2007 SP1，我们将AMT技术整合到SCCM产品之中，此模块被称为Out of Band Management feature。上海研发团队主导了这部分功能的所有设计，开发工作。
SCCM Out of Band Management结合了AMT在硬件层面的强大功能，并依托了SCCM平台中强有力的企业机器管理模式，为企业提供了灵活、便捷、强大的远程唤醒、远程技术支持、资产管理、、灾难恢复等功能。
Overview of Out of Band Management
Topic last updated—May 2008
http://technet.microsoft.com/en-us/library/cc161963.aspx
Out of band management in Configuration Manager 2007 SP1 provides powerful management control for computers that have the Intel vPro chip set and Intel Active Management Technology (Intel AMT) firmware versions 3.2.1 or later.
Out of band management allows an administrator to connect to a computer's management controller when the computer is turned off, in sleep or hibernate modes, or otherwise unresponsive through the operating system. By way of contrast, in-band management is the classic approach used by Configuration Manager and its predecessors whereby an agent runs in the full operating system on the managed computer and the management controller accomplishes tasks by communicating with the management agent.
Out of band management supplements in-band management. While in-band management supports a wider range of operations because its environment is the full operating system, in-band management might not be functional if the operating system is not present or is not operational. In these situations, the supplementary capabilities of out of band management allow administrators to manage these computers without requiring local access to the computer.
Out of Band Management简介 —— SCCM 2007 Out of Band Management专题系列之一
Out of Band Management正在逐步成为IT管理的主流技术，本专题系列计划就SCCM 2007中Out of Band Management feature做一些介绍和探讨，来帮助读者了解并使用SCCM 2007中的Out of Band Management技术，系列将包括简介，使用，调错等专题文章。
Out of Band Management简介
Out of Band Management是指带外管理技术，是一种不依赖于操作系统就可对目标机器进行管理的技术，目前Intel的AMT（Active Management Technology）和DASH标准（Desktop and mobile Architecture for System Hardware）都提供了Out of Band Management的支持。 在SCCM 2007 SP1，我们将AMT技术整合到SCCM产品之中，此模块被称为Out of Band Management feature。上海研发团队主导了这部分功能的所有设计，开发工作。
SCCM Out of Band Management结合了AMT在硬件层面的强大功能，并依托了SCCM平台中强有力的企业机器管理模式，为企业提供了灵活、便捷、强大的远程唤醒、远程技术支持、资产管理、、灾难恢复等功能。
Overview of Out of Band Management
Topic last updated—May 2008
http://technet.microsoft.com/en-us/library/cc161963.aspx
Out of band management in Configuration Manager 2007 SP1 provides powerful management control for computers that have the Intel vPro chip set and Intel Active Management Technology (Intel AMT) firmware versions 3.2.1 or later.
Out of band management allows an administrator to connect to a computer's management controller when the computer is turned off, in sleep or hibernate modes, or otherwise unresponsive through the operating system. By way of contrast, in-band management is the classic approach used by Configuration Manager and its predecessors whereby an agent runs in the full operating system on the managed computer and the management controller accomplishes tasks by communicating with the management agent.
Out of band management supplements in-band management. While in-band management supports a wider range of operations because its environment is the full operating system, in-band management might not be functional if the operating system is not present or is not operational. In these situations, the supplementary capabilities of out of band management allow administrators to manage these computers without requiring local access to the computer.
2009-01-22
Content location request for apps package failed. (Code 0x80040102)
Got error during SCCM deployment:
Content location request for apps package failed. (Code 0x80040102)
Information from Microsoft about this code:
Error code 0x80040102: No content location returned for the given package
solution:
Check the server side to make sure the package is distributed to at least one distribution point. Also check whether advertisement allows the task sequence to fall back to remote distribution point when there is no local distribution point
Troubleshooting Operating System Deployment Using Custom Error Codes
http://technet.microsoft.com/en-us/library/bb735886.aspx
Custom Error Codes for Configuration Manager 2007
http://technet.microsoft.com/en-us/library/bb632794.aspx
This fixed my problem:
Configuration manager->site database->computer management->software distribution -> advertisements -> right click on the advertisement you want to edit and choose properties -> "distribution points" Tab -> tick "when no local distribution points is available, use a remote distribution point" and "when no protected distribution point is available, use an unprotected distribution point.
Save and restart the build again.
Content location request for apps package failed. (Code 0x80040102)
Information from Microsoft about this code:
Error code 0x80040102: No content location returned for the given package
solution:
Check the server side to make sure the package is distributed to at least one distribution point. Also check whether advertisement allows the task sequence to fall back to remote distribution point when there is no local distribution point
Troubleshooting Operating System Deployment Using Custom Error Codes
http://technet.microsoft.com/en-us/library/bb735886.aspx
Custom Error Codes for Configuration Manager 2007
http://technet.microsoft.com/en-us/library/bb632794.aspx
This fixed my problem:
Configuration manager->site database->computer management->software distribution -> advertisements -> right click on the advertisement you want to edit and choose properties -> "distribution points" Tab -> tick "when no local distribution points is available, use a remote distribution point" and "when no protected distribution point is available, use an unprotected distribution point.
Save and restart the build again.
2009-01-12
Joining a domain during an SCCM OS deployment
Inside ConfigMgr 07 Operating System Deployment
http://blogs.technet.com/inside_osd/Default.aspx?p=2
Joining a Domain: Epilogue
http://blogs.technet.com/inside_osd/archive/2007/06/29/joining-a-domain-epilogue.aspx
Joining a Domain, Part 2
http://blogs.technet.com/inside_osd/archive/2007/06/26/joining-a-domain-part-2.aspx
Joining a domain during an OS deployment
http://blogs.technet.com/inside_osd/archive/2007/06/22/joining-a-domain-during-an-os-deployment.aspx
http://blogs.technet.com/inside_osd/Default.aspx?p=2
Joining a Domain: Epilogue
http://blogs.technet.com/inside_osd/archive/2007/06/29/joining-a-domain-epilogue.aspx
Joining a Domain, Part 2
http://blogs.technet.com/inside_osd/archive/2007/06/26/joining-a-domain-part-2.aspx
Joining a domain during an OS deployment
http://blogs.technet.com/inside_osd/archive/2007/06/22/joining-a-domain-during-an-os-deployment.aspx
2009-01-09
Ports used by Configuration Manager
Ports used by Configuration Manager
http://technet.microsoft.com/en-us/library/bb632618.aspx
Client to MP: 80 mixed mode, 443 for native mode
Client to SUP: 80/8530 or 443/8531
Client to DP: 80/443 and 445 (SMB)
Client to SLP: 80
You should also take into account that workstations may (and should) have Windows Firewall enabled.
Firewall Settings for Configuration Manager Clients
http://technet.microsoft.com/en-us/library/bb694088.aspx
Also clients need to be installed first. If you plan to use Client Push, I believe ports for RPC and Kerberos should be opened. Or you can use logon scripts.
However the ports used depend on the features that you plan to use in your infrastructure. Best option in my opinion is to try to implement Native Mode. Then all the communication with the clients will use 443 (SSL).
As a matter of fact I am struggling to configure it myself right now :-)
More info here:
Choose between Native Mode and Mixed Mode
http://technet.microsoft.com/en-us/library/bb632431.aspx
http://technet.microsoft.com/en-us/library/bb632618.aspx
Client to MP: 80 mixed mode, 443 for native mode
Client to SUP: 80/8530 or 443/8531
Client to DP: 80/443 and 445 (SMB)
Client to SLP: 80
You should also take into account that workstations may (and should) have Windows Firewall enabled.
Firewall Settings for Configuration Manager Clients
http://technet.microsoft.com/en-us/library/bb694088.aspx
Also clients need to be installed first. If you plan to use Client Push, I believe ports for RPC and Kerberos should be opened. Or you can use logon scripts.
However the ports used depend on the features that you plan to use in your infrastructure. Best option in my opinion is to try to implement Native Mode. Then all the communication with the clients will use 443 (SSL).
As a matter of fact I am struggling to configure it myself right now :-)
More info here:
Choose between Native Mode and Mixed Mode
http://technet.microsoft.com/en-us/library/bb632431.aspx
2008-12-31
SMS2003部署及troubleshooting
http://struggle.blog.51cto.com/333093/79354
详解SMS2003部署Windows 2003
http://www.winsvr.org/info/info.php?sessid=&infoid=32&page=1
SMS 2003安装配置系列之一:SMS 2003主站点安装指南
http://www.ixpub.net/archiver/tid-658413.html
解读SMS2003日志文件
http://www.microsoft.com/technet/sms/2003/library/techfaq/tfaq03.mspx#EWEAC
Clients Frequently Asked Questions
http://www.ixpub.net/thread-658378-1-7.html
如何解决在 Systems Management Server 2003 高级客户端推送安装问题
http://www.microsoft.com/technet/scriptcenter/guide/sas_roa_overview.mspx?mfr=true
Microsoft Windows 2000 Scripting Guide
http://technet.microsoft.com/en-us/library/cc179974%28TechNet.10%29.aspx
Scripting in SMS
http://support.microsoft.com/kb/883620
You cannot install Advanced Client when your Systems Management Server 2003 does not use Active Directory or when the schema for Active Directory has not been extended
http://support.microsoft.com/kb/925282
How to troubleshoot Advanced Client Push Installation issues in Systems Management Server 2003
http://www.tek-tips.com/viewthread.cfm?qid=1151166&page=1
解决sms客户端无法安装的问题，如何检查DC之间的复制是否成功。
http://technet.microsoft.com/en-us/library/cc181833%28TechNet.10%29.aspx
technet resource: Systems Management Server 2003
详解SMS2003部署Windows 2003
http://www.winsvr.org/info/info.php?sessid=&infoid=32&page=1
SMS 2003安装配置系列之一:SMS 2003主站点安装指南
http://www.ixpub.net/archiver/tid-658413.html
解读SMS2003日志文件
http://www.microsoft.com/technet/sms/2003/library/techfaq/tfaq03.mspx#EWEAC
Clients Frequently Asked Questions
http://www.ixpub.net/thread-658378-1-7.html
如何解决在 Systems Management Server 2003 高级客户端推送安装问题
http://www.microsoft.com/technet/scriptcenter/guide/sas_roa_overview.mspx?mfr=true
Microsoft Windows 2000 Scripting Guide
http://technet.microsoft.com/en-us/library/cc179974%28TechNet.10%29.aspx
Scripting in SMS
http://support.microsoft.com/kb/883620
You cannot install Advanced Client when your Systems Management Server 2003 does not use Active Directory or when the schema for Active Directory has not been extended
http://support.microsoft.com/kb/925282
How to troubleshoot Advanced Client Push Installation issues in Systems Management Server 2003
http://www.tek-tips.com/viewthread.cfm?qid=1151166&page=1
解决sms客户端无法安装的问题，如何检查DC之间的复制是否成功。
http://technet.microsoft.com/en-us/library/cc181833%28TechNet.10%29.aspx
technet resource: Systems Management Server 2003
Force SCCM client to check advertisements
System ManagementCustomize SMS Using Local Policies
http://technet.microsoft.com/en-us/magazine/2006.09.customizesms.aspx
Force Task Sequence Execution without Advertisement
http://social.technet.microsoft.com/Forums/en-US/configmgrsdk/thread/298b32f6-746c-473a-b7ce-6bb51cfe1270/
Force SCCM Client to Check for New Advertisements
http://social.technet.microsoft.com/Forums/en-US/configmgrswdist/thread/a1066dfb-a71e-4e52-b7b7-c225ea0935a4/
http://technet.microsoft.com/en-us/magazine/2006.09.customizesms.aspx
Force Task Sequence Execution without Advertisement
http://social.technet.microsoft.com/Forums/en-US/configmgrsdk/thread/298b32f6-746c-473a-b7ce-6bb51cfe1270/
Force SCCM Client to Check for New Advertisements
http://social.technet.microsoft.com/Forums/en-US/configmgrswdist/thread/a1066dfb-a71e-4e52-b7b7-c225ea0935a4/
Control SCCM client actions by scripting
The Advanced Client, is scriptable. You can use the CPApplet locally on the client or you can use WMI to do things remotely. On thing you'll often need is the triggering of an action. There are loads of samples in this forum meanwhile how to do it. Here is an overview of the actions available and their respective ScheduledMessageIDs which you will need to trigger them remotely.
(From http://www.myitforum.com/articles/8/view.asp?id=6757)
Hardware Inventory Cycle
CPApplet Name: Hardware Inventory Collection Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000001}
Software Inventory Cycle
CPApplet Name: Software Inventory Collection Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000002}
Discovery Data Collection Cycle
CPApplet Name: Discovery Data Collection Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000003}
File Collection Cycle
CPApplet Name: Standard File Collection Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000010}
ID MIF Collection Cycle
CPApplet Name: Standard File Collection Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000011}
Machine Policy Retrieval & Evaluation Cycle
CPApplet Name: Request & Evaluate Machine Policy
ScheduledMessageID: {00000000-0000-0000-0000-00000021} RequestAssignments Resource Type=’Machine’
ScheduledMessageID: {00000000-0000-0000-0000-00000022} Evaluate Policy Resource Type=’Machine’
The Machine Policy Retrieval & Evaluation Cycle consists of these two actions! There are two more Scheduled Messages in this context with no corresponding Client Actions.
ScheduledMessageID: {00000000-0000-0000-0000-00000040} CleanupPolicy Resource Type=’Machine’
ScheduledMessageID: {00000000-0000-0000-0000-00000042} ValidateAssignments Resource Type=’Machine’
User Policy Retrieval & Evaluation Cycle
CPApplet Name: Request & Evaluate User Policy
ScheduledMessageID: {00000000-0000-0000-0000-00000026} RequestAssignments Resource Type=’User’
ScheduledMessageID: {00000000-0000-0000-0000-00000027} Evaluate Policy Resource Type=’User’
The User Policy Retrieval & Evaluation Cycle consists of these two actions! There are two more Scheduled Messages in this context.
ScheduledMessageID: {00000000-0000-0000-0000-00000041} CleanupPolicy Resource Type=’User’
ScheduledMessageID: {00000000-0000-0000-0000-00000043} ValidateAssignments Resource Type=’User’
Software Metering Usage Report Cycle
CPApplet Name: Software Metering Usage Report Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000031}
Windows Installer Source List Update Cycle
CPApplet Name: MSI Product Source Update Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000032}
There are a few Scheduled Messages that do not correspond to Client Actions that can be triggered via the GUI.
Refresh default MP
ScheduledMessageID: {00000000-0000-0000-0000-00000023} LSRefreshDefaultMPTask
Refresh Location
ScheduledMessageID: {00000000-0000-0000-0000-00000024} LSRefreshLocationsTask
Timeout Location Service Requests
ScheduledMessageID: {00000000-0000-0000-0000-00000025} LSTimeOutRequestsTask
Manage Certificates
ScheduledMessageID: {00000000-0000-0000-0000-00000051} CertMaintenance
(From http://www.myitforum.com/articles/8/view.asp?id=6757)
Hardware Inventory Cycle
CPApplet Name: Hardware Inventory Collection Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000001}
Software Inventory Cycle
CPApplet Name: Software Inventory Collection Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000002}
Discovery Data Collection Cycle
CPApplet Name: Discovery Data Collection Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000003}
File Collection Cycle
CPApplet Name: Standard File Collection Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000010}
ID MIF Collection Cycle
CPApplet Name: Standard File Collection Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000011}
Machine Policy Retrieval & Evaluation Cycle
CPApplet Name: Request & Evaluate Machine Policy
ScheduledMessageID: {00000000-0000-0000-0000-00000021} RequestAssignments Resource Type=’Machine’
ScheduledMessageID: {00000000-0000-0000-0000-00000022} Evaluate Policy Resource Type=’Machine’
The Machine Policy Retrieval & Evaluation Cycle consists of these two actions! There are two more Scheduled Messages in this context with no corresponding Client Actions.
ScheduledMessageID: {00000000-0000-0000-0000-00000040} CleanupPolicy Resource Type=’Machine’
ScheduledMessageID: {00000000-0000-0000-0000-00000042} ValidateAssignments Resource Type=’Machine’
User Policy Retrieval & Evaluation Cycle
CPApplet Name: Request & Evaluate User Policy
ScheduledMessageID: {00000000-0000-0000-0000-00000026} RequestAssignments Resource Type=’User’
ScheduledMessageID: {00000000-0000-0000-0000-00000027} Evaluate Policy Resource Type=’User’
The User Policy Retrieval & Evaluation Cycle consists of these two actions! There are two more Scheduled Messages in this context.
ScheduledMessageID: {00000000-0000-0000-0000-00000041} CleanupPolicy Resource Type=’User’
ScheduledMessageID: {00000000-0000-0000-0000-00000043} ValidateAssignments Resource Type=’User’
Software Metering Usage Report Cycle
CPApplet Name: Software Metering Usage Report Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000031}
Windows Installer Source List Update Cycle
CPApplet Name: MSI Product Source Update Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000032}
There are a few Scheduled Messages that do not correspond to Client Actions that can be triggered via the GUI.
Refresh default MP
ScheduledMessageID: {00000000-0000-0000-0000-00000023} LSRefreshDefaultMPTask
Refresh Location
ScheduledMessageID: {00000000-0000-0000-0000-00000024} LSRefreshLocationsTask
Timeout Location Service Requests
ScheduledMessageID: {00000000-0000-0000-0000-00000025} LSTimeOutRequestsTask
Manage Certificates
ScheduledMessageID: {00000000-0000-0000-0000-00000051} CertMaintenance
Force SCCM clients to check for new program advertisements
Q: How can I force my SCCM clients to check for new program advertisements?
A: Program advertisements occur as part of the Machine Policy Retrieval & Evaluation cycle action in the SCCM Client.
To force a client to find new programs that are available ahead of the regular discovery phase, perform these steps:
1. Start the Systems Management Control Panel applet (Start, Settings, Control Panel, Configuration Manager).
2. Click the Actions tab.
3. Select "Machine Policy Retrieval & Evaluation Cycle" and click Initiate Action.
4. Close the Systems Management Control Panel applet. Within a few minutes, the new-program advertisements should be visible. Alternatively, you can use the Policy Spy Tool to force a Machine policy retrieval. You can download the Policy Spy Tool at http://www.microsoft.com/smserver/downloads/2003/tools/toolkit.asp.
Q: When you distribute sw to user collections what triggers the installation?
A: It is the "User policy retrieval and evaluation cycle" that triggers the installationThe interval of "User policy retrieval and evaluation cycle" is defined in the Computer Client Agent properties on the SCCM server:
(http://technet.microsoft.com/en-us/library/bb693764.aspx)
SCCM console -> site management-> site name XXXX -> site settings -> client agents -> right click
By default it’s 60 minutes.
A: Program advertisements occur as part of the Machine Policy Retrieval & Evaluation cycle action in the SCCM Client.
To force a client to find new programs that are available ahead of the regular discovery phase, perform these steps:
1. Start the Systems Management Control Panel applet (Start, Settings, Control Panel, Configuration Manager).
2. Click the Actions tab.
3. Select "Machine Policy Retrieval & Evaluation Cycle" and click Initiate Action.
4. Close the Systems Management Control Panel applet. Within a few minutes, the new-program advertisements should be visible. Alternatively, you can use the Policy Spy Tool to force a Machine policy retrieval. You can download the Policy Spy Tool at http://www.microsoft.com/smserver/downloads/2003/tools/toolkit.asp.
Q: When you distribute sw to user collections what triggers the installation?
A: It is the "User policy retrieval and evaluation cycle" that triggers the installationThe interval of "User policy retrieval and evaluation cycle" is defined in the Computer Client Agent properties on the SCCM server:
(http://technet.microsoft.com/en-us/library/bb693764.aspx)
SCCM console -> site management-> site name XXXX -> site settings -> client agents -> right click
By default it’s 60 minutes.
2008-12-22
BDD 2007 - Troubleshooting Database issues
BDD 2007 - Troubleshooting Database issues
(Original from Ben Hunter's blog, check more details from this link:
http://blogs.technet.com/benhunter/archive/2007/07/10/bdd-2007-troubleshooting-database-issues.aspx)
Common issues
The following section details common issues and recommended configurations for each.
Database Rules - Ensure that the appropriate database rules have been created. Database rules are specified using the deployment point rules tab. Configuration database rules can be created manually or using the Configure DB Wizard in the Deployment Workbench.
A typical database section should look similar to the following:
[CSettings]
SQLServer=SERVERNAME
Database=BDDAdminDB
Netlib=DBNMPNTW
SQLShare=logs
Table=ComputerSettings
Parameters=MacAddress
ParameterCondition=OR
The critical components of the database section are:
SQLServer - must specify the SQL server that hosts the BDD configuration database. SQLShare – must be a valid share on the SQL server and the user account (UserID as specified in the rules) must have access rights to that share. If SMS OSD Feature Pack is used for deployment then the SMS Advanced Client installation account will require access rights rather than the user account. Netlib – there are many issues with using TCP/IP sockets based connections so ONLY USE NAMED PIPES (DBNMPNTW).Database connectivity issues – There are a number of issues that can stop the client connecting to the SQL server, these are detailed below:
Ensure that Named Pipes is enabled for remote connectivity on the SQL server, this is not enabled by default. Has the surface area been configured to enable Named Pipes? When using SQL 2005 it is important to ensure that the “Surface area” is configured in such a way that remote connectivity to Named Pipes is allowed. If you have issues accessing the database from the workbench then ensure that you are using Named Pipes. The Deployment Workbench always uses Named Pipes to connect to the database.Security - has the deployment account got the appropriate database rights? The account used will need read rights to the BDD admin database. The account can vary depending on the deployment type:
ZTI – The SMS advanced client installation account. LTI – The user account specified in the rules (bootstrap.ini).SQL instances – If you are connecting to a database instance then this instance must be specified. This value is specified using the Instance field in the deployment workbench
Troubleshooting methods
During the troubleshooting process it is critical that you can easily test the database rules. The following instructions detail how to manually test the database connectivity. The rules specified in the deployment point can be tested without running through the entire BDD build process. Rules are processed using a script called ZTIGather.wsf, this script can be run separately from the other BDD scripts allowing easy testing. The steps below detail the process required to perform manual rule testing. To properly reflect the deployment environment it is important to perform these tests from a client device:
1. Create a folder on the client device and copy the following files from the deployment point to this folder:
ZTIGather.wsf ZTIGather.xml ZTIUtility.vbs CustomSettings.ini 2. Delete C:\MININT directory if it already exists. This folder can also be located at X:\MININT if the C drive is not available.
NOTE: BDD stores configuration and progress information in the MININT folder, if this folder is not removed between tests then the results will be invalid.
3. From the command prompt navigate to the newly created folder and execute the rule processing script using the following command:
"cscript.exe ZTIGather.wsf /debug:true"
The script will then be processed and the results outputted to the command prompt and a log file ( .\MININT\SMSOSD\OSDLOGS\ZTIGather.log)
(Original from Ben Hunter's blog, check more details from this link:
http://blogs.technet.com/benhunter/archive/2007/07/10/bdd-2007-troubleshooting-database-issues.aspx)
Common issues
The following section details common issues and recommended configurations for each.
Database Rules - Ensure that the appropriate database rules have been created. Database rules are specified using the deployment point rules tab. Configuration database rules can be created manually or using the Configure DB Wizard in the Deployment Workbench.
A typical database section should look similar to the following:
[CSettings]
SQLServer=SERVERNAME
Database=BDDAdminDB
Netlib=DBNMPNTW
SQLShare=logs
Table=ComputerSettings
Parameters=MacAddress
ParameterCondition=OR
The critical components of the database section are:
SQLServer - must specify the SQL server that hosts the BDD configuration database. SQLShare – must be a valid share on the SQL server and the user account (UserID as specified in the rules) must have access rights to that share. If SMS OSD Feature Pack is used for deployment then the SMS Advanced Client installation account will require access rights rather than the user account. Netlib – there are many issues with using TCP/IP sockets based connections so ONLY USE NAMED PIPES (DBNMPNTW).Database connectivity issues – There are a number of issues that can stop the client connecting to the SQL server, these are detailed below:
Ensure that Named Pipes is enabled for remote connectivity on the SQL server, this is not enabled by default. Has the surface area been configured to enable Named Pipes? When using SQL 2005 it is important to ensure that the “Surface area” is configured in such a way that remote connectivity to Named Pipes is allowed. If you have issues accessing the database from the workbench then ensure that you are using Named Pipes. The Deployment Workbench always uses Named Pipes to connect to the database.Security - has the deployment account got the appropriate database rights? The account used will need read rights to the BDD admin database. The account can vary depending on the deployment type:
ZTI – The SMS advanced client installation account. LTI – The user account specified in the rules (bootstrap.ini).SQL instances – If you are connecting to a database instance then this instance must be specified. This value is specified using the Instance field in the deployment workbench
Troubleshooting methods
During the troubleshooting process it is critical that you can easily test the database rules. The following instructions detail how to manually test the database connectivity. The rules specified in the deployment point can be tested without running through the entire BDD build process. Rules are processed using a script called ZTIGather.wsf, this script can be run separately from the other BDD scripts allowing easy testing. The steps below detail the process required to perform manual rule testing. To properly reflect the deployment environment it is important to perform these tests from a client device:
1. Create a folder on the client device and copy the following files from the deployment point to this folder:
ZTIGather.wsf ZTIGather.xml ZTIUtility.vbs CustomSettings.ini 2. Delete C:\MININT directory if it already exists. This folder can also be located at X:\MININT if the C drive is not available.
NOTE: BDD stores configuration and progress information in the MININT folder, if this folder is not removed between tests then the results will be invalid.
3. From the command prompt navigate to the newly created folder and execute the rule processing script using the following command:
"cscript.exe ZTIGather.wsf /debug:true"
The script will then be processed and the results outputted to the command prompt and a log file ( .\MININT\SMSOSD\OSDLOGS\ZTIGather.log)
List of Log Files in Configuration Manager 2007
http://technet.microsoft.com/en-us/library/bb892800.aspx
List of Log Files in Configuration Manager 2007
All the client and site server components in Microsoft System Center Configuration Manager 2007 record process information in individual log files. You can use the information in the client and site server log files to help you troubleshoot issues that might occur in your Configuration Manager 2007 hierarchy.
By default, client and server component logging is turned on in Configuration Manager 2007.
Client Log FilesThe Configuration Manager 2007 client logs are located in one of the following locations:
On computers that serve as management points, the client logs are located in the SMS_CCM\Logs folder.
On all other computers, the client log files are located in the %Windir%\System32\CCM\Logs folder or the %Windir%\SysWOW64\CCM\Logs.
Site Server Log FilesMost Configuration Manager 2007 site server log files are located in the\LOGS folder. Because Configuration Manager 2007 relies heavily on Microsoft Internet Information Services (IIS), you can review the IIS log file for additional errors that relate to client access to the IIS server. The IIS log file is located in the %Windir%\System32\logfiles\W3SVC1 folder on the IIS server.
Management Point Log FilesIf management points are installed in the site hierarchy, management point log files are stored in the SMS_CCM\LOGS folder on the management point computer.
Network Access Protection Log FilesBy default, client log files related to Network Access Protection are found in %windir%\CCM\Logs. For client computers that are also management points, the log files are found in %ProgramFiles%\SMS_CCM\Logs.
The System Health Validator point log files are located in %systemdrive%\SMSSHV\SMS_SHV\Logs.
Desired Configuration Management Log FilesBy default, the Configuration Manager 2007 client computer log files are found in %windir%\System32\CCM\Logs or in %windir%\SysWOW64\CCM\Logs. For client computers that are also management points, the client log files are located in the SMS_CCM\Logs folder. The following table lists and describes these log files.
Wake On LAN Log FilesThe Configuration Manager 2007 site server log files related to Wake On LAN are located in the folder\Logs on the site server.
Software Updates Site Server Log FilesThe Configuration Manager 2007 site server log files are found, by default, in\Logs.
WSUS Server Log FilesBy default, the log files for WSUS running on the software update point site system role are found in %ProgramFiles%\Update Services\LogFiles.
Software Updates Client Computer Log FilesBy default, the Configuration Manager 2007 client computer log files are found in %windir%\CCM\Logs.
Windows Update Agent Log FileBy default, the Windows Update Agent log file is found on the Configuration Manager Client computer in %windir%.
Out of Band Service Point Log FilesThe Configuration Manager 2007 SP1 log files listed in the following table are located in the folder\Logs on the site system server selected to host the out of band service point role.
Out of Band Management Console Log FilesThe Configuration Manager 2007 SP1 log file listed in the following table is located in the folder\AdminUI\AdminUILog on any computer that runs the out of band management console from the Configuration Manager console.
Out of Band Client Computer Log FilesThe Configuration Manager 2007 SP1 log file listed in the following table is located in the folder %windir%\System32\CCM\Logs on workstation computers that are running the Configuration Manager 2007 SP1 client and that are managed out of band.
List of Log Files in Configuration Manager 2007
All the client and site server components in Microsoft System Center Configuration Manager 2007 record process information in individual log files. You can use the information in the client and site server log files to help you troubleshoot issues that might occur in your Configuration Manager 2007 hierarchy.
By default, client and server component logging is turned on in Configuration Manager 2007.
Client Log FilesThe Configuration Manager 2007 client logs are located in one of the following locations:
On computers that serve as management points, the client logs are located in the SMS_CCM\Logs folder.
On all other computers, the client log files are located in the %Windir%\System32\CCM\Logs folder or the %Windir%\SysWOW64\CCM\Logs.
Site Server Log FilesMost Configuration Manager 2007 site server log files are located in the
Management Point Log FilesIf management points are installed in the site hierarchy, management point log files are stored in the SMS_CCM\LOGS folder on the management point computer.
Network Access Protection Log FilesBy default, client log files related to Network Access Protection are found in %windir%\CCM\Logs. For client computers that are also management points, the log files are found in %ProgramFiles%\SMS_CCM\Logs.
The System Health Validator point log files are located in %systemdrive%\SMSSHV\SMS_SHV\Logs.
Desired Configuration Management Log FilesBy default, the Configuration Manager 2007 client computer log files are found in %windir%\System32\CCM\Logs or in %windir%\SysWOW64\CCM\Logs. For client computers that are also management points, the client log files are located in the SMS_CCM\Logs folder. The following table lists and describes these log files.
Wake On LAN Log FilesThe Configuration Manager 2007 site server log files related to Wake On LAN are located in the folder
Software Updates Site Server Log FilesThe Configuration Manager 2007 site server log files are found, by default, in
WSUS Server Log FilesBy default, the log files for WSUS running on the software update point site system role are found in %ProgramFiles%\Update Services\LogFiles.
Software Updates Client Computer Log FilesBy default, the Configuration Manager 2007 client computer log files are found in %windir%\CCM\Logs.
Windows Update Agent Log FileBy default, the Windows Update Agent log file is found on the Configuration Manager Client computer in %windir%.
Out of Band Service Point Log FilesThe Configuration Manager 2007 SP1 log files listed in the following table are located in the folder
Out of Band Management Console Log FilesThe Configuration Manager 2007 SP1 log file listed in the following table is located in the folder
Out of Band Client Computer Log FilesThe Configuration Manager 2007 SP1 log file listed in the following table is located in the folder %windir%\System32\CCM\Logs on workstation computers that are running the Configuration Manager 2007 SP1 client and that are managed out of band.
Troubleshooting Tips for SCCM deployment
http://blogs.technet.com/inside_osd/archive/2007/12/13/troubleshooting-tips.aspx
Inside ConfigMgr 07 Operating System Deployment
Contributed by Brett Flegg
Troubleshooting Tips
The follow is a collection of tips that may be helpful when troubleshooting issues with ConfigMgr 07 Operating System Deployment.
Error Codes
There is no definitive list of error codes that can be returned in a task sequence, because most of the error codes originate from calls to other Windows API functions. The error lookup functionality provided by trace32.exe is a good place to start when trying to figure out what a specific error code means (in trace32.exe, go to Tools / Error Lookup...).
Enable the Debug Shell on your boot image
Boot images have an option to enable a command shell while running in Windows PE. This is turned off by default for security reasons (since it would allow an end user to open a command shell during the re-imaging process) but can be enabled on the “Windows PE” property page.
Open the boot image’s properties dialogOn the Windows PE tab check the “Enable command support (testing only)” optionUpdate the boot image on the distribution pointsRebuild any media that uses the boot image (e.g. capture media, boot media, or stand-alone media)When a task sequence is running in Windows PE you can open a command shell by pressing F8. As long as the command-shell is open the task sequence will not reboot the machine. This will give you a chance to verify network connectivity, diagnose driver issues, and view/copy the log files (see Client Log Files section below).
Client Log Files
All actions in a task sequence log to the smsts.log file. This file is moved around during different stages of an operating system deployment so that it does not interfere with the imaging process.
While in Windows PE the log file is stored in the windows temp directory on the RAM-disk (typically x:\windows\temp\smstslog)While in a full operating system that has a ConfigMgr client installed the log file is located in the smstslog subdirectory under the client logging path (typically %windir%\system32\ccm\logs\smstslog)While in the full operating system that does not have a ConfigMgr client installed the log file is located in the Windows temp directory (typically %windir%\temp\smstslog)When the task sequence completes, the log file is “finalized” to one of the following locations depending on the state of the machine:
If the task sequence finishes in Windows PE the log file is copied to an SMSTSLog directory on the largest available partition.If the task sequence finishes in the full operating system and a ConfigMgr client is installed then the log is copied to the client logging path (typically %windir%\system32\ccm\logs)If the task sequence finishes in the full operating system and there is no ConfigMgr client installed then the log is copied to the Windows temp directory.
Task Sequence Reports
When running, task sequences send status messages back to the server for each step in the task sequence. Included in these status messages are the last 1024 characters of stdout/stderr text from the action. Many times, this information can be used to remotely diagnose a task sequence issue (especially useful if an error has occurred in Windows PE and the debug shell was not enabled). The “History - Specific task sequence advertisements run on a specific computer” report provides a list of these status messages for a specific advertisement and computer and can be opened from the Reports node in the ConfigMgr console.
Inside ConfigMgr 07 Operating System Deployment
Contributed by Brett Flegg
Troubleshooting Tips
The follow is a collection of tips that may be helpful when troubleshooting issues with ConfigMgr 07 Operating System Deployment.
Error Codes
There is no definitive list of error codes that can be returned in a task sequence, because most of the error codes originate from calls to other Windows API functions. The error lookup functionality provided by trace32.exe is a good place to start when trying to figure out what a specific error code means (in trace32.exe, go to Tools / Error Lookup...).
Enable the Debug Shell on your boot image
Boot images have an option to enable a command shell while running in Windows PE. This is turned off by default for security reasons (since it would allow an end user to open a command shell during the re-imaging process) but can be enabled on the “Windows PE” property page.
Open the boot image’s properties dialogOn the Windows PE tab check the “Enable command support (testing only)” optionUpdate the boot image on the distribution pointsRebuild any media that uses the boot image (e.g. capture media, boot media, or stand-alone media)When a task sequence is running in Windows PE you can open a command shell by pressing F8. As long as the command-shell is open the task sequence will not reboot the machine. This will give you a chance to verify network connectivity, diagnose driver issues, and view/copy the log files (see Client Log Files section below).
Client Log Files
All actions in a task sequence log to the smsts.log file. This file is moved around during different stages of an operating system deployment so that it does not interfere with the imaging process.
While in Windows PE the log file is stored in the windows temp directory on the RAM-disk (typically x:\windows\temp\smstslog)While in a full operating system that has a ConfigMgr client installed the log file is located in the smstslog subdirectory under the client logging path (typically %windir%\system32\ccm\logs\smstslog)While in the full operating system that does not have a ConfigMgr client installed the log file is located in the Windows temp directory (typically %windir%\temp\smstslog)When the task sequence completes, the log file is “finalized” to one of the following locations depending on the state of the machine:
If the task sequence finishes in Windows PE the log file is copied to an SMSTSLog directory on the largest available partition.If the task sequence finishes in the full operating system and a ConfigMgr client is installed then the log is copied to the client logging path (typically %windir%\system32\ccm\logs)If the task sequence finishes in the full operating system and there is no ConfigMgr client installed then the log is copied to the Windows temp directory.
Task Sequence Reports
When running, task sequences send status messages back to the server for each step in the task sequence. Included in these status messages are the last 1024 characters of stdout/stderr text from the action. Many times, this information can be used to remotely diagnose a task sequence issue (especially useful if an error has occurred in Windows PE and the debug shell was not enabled). The “History - Specific task sequence advertisements run on a specific computer” report provides a list of these status messages for a specific advertisement and computer and can be opened from the Reports node in the ConfigMgr console.
2008-12-09
Create a shortcut using the runas command
A command prompt with administrative credentials:
runas /user: ComputerName\administrator cmd
Computer Management with administrative credentials: runas /user:ComputerName\administrator "mmc %windir%\system32\compmgmt.msc"
Active Directory Users and Computers with domain administrative credentials: runas /user:DomainName\administrator "mmc %windir%\system32\dsa.msc"
Active Directory Users and Computers in another forest: runas /netonly /user:DomainName\UserName"mmc %windir%\system32\dsa.msc"
runas /user: ComputerName\administrator cmd
Computer Management with administrative credentials: runas /user:ComputerName\administrator "mmc %windir%\system32\compmgmt.msc"
Active Directory Users and Computers with domain administrative credentials: runas /user:DomainName\administrator "mmc %windir%\system32\dsa.msc"
Active Directory Users and Computers in another forest: runas /netonly /user:DomainName\UserName"mmc %windir%\system32\dsa.msc"
2008-11-26
how to check if your mail server on the spam black list
http://spamlinks.net/filter-dnsbl-lookup.htm#general-sites
http://www.emailtools.co.uk/tips/blacklists.htm
Check email black list tool
http://www.emailtools.co.uk/tools/blacklistcheck.htm
http://openrbl.org/query?i=xxx.xxx.xx.xxx
http://dnsbl.njabl.org/cgi-bin/lookup.cgi?query=xxx.xxx.xxx.xxx
http://www.junkemailfilter.com
http://www.mxtoolbox.com/blacklists.aspx
Check exchange server smtp log:
http://www.msexchange.org/tutorials/Logging_the_SMTP_Service.html
Stop Spam From the Inside by Locking Down SMTP:
http://technet.microsoft.com/en-au/magazine/cc161029.aspx
http://www.emailtools.co.uk/tips/blacklists.htm
Check email black list tool
http://www.emailtools.co.uk/tools/blacklistcheck.htm
http://openrbl.org/query?i=xxx.xxx.xx.xxx
http://dnsbl.njabl.org/cgi-bin/lookup.cgi?query=xxx.xxx.xxx.xxx
http://www.junkemailfilter.com
http://www.mxtoolbox.com/blacklists.aspx
Check exchange server smtp log:
http://www.msexchange.org/tutorials/Logging_the_SMTP_Service.html
Stop Spam From the Inside by Locking Down SMTP:
http://technet.microsoft.com/en-au/magazine/cc161029.aspx
2008-11-24
troubleshooting computer browser problem
You are experience one of the following errors:
1. Got error when run netdiag on a DC:
DC list test . . . . . . . . . . . : Failed
Failed to enumerate DCs by using the browser. [ERROR_NO_BROWSER_SERVERS_
FOUND]
2. Got "conflict" netbios info when run "nbtstat -n
3. Got error when run "browstat status":
Status for domain LGSYDNEY on transport \Device\NetBT_Tcpip_{6F7C3E8B-4519-4BA6-
AF4B-B4BB15621181}
Browsing is NOT active on domain. Status : 6118
Master browser name is held by: SSFILE01
Master browser is running build 3790
Status for domain LGSYDNEY on transport \Device\NetBT_Tcpip_{1DB6AA0C-F123-4B47-
9B57-E2DC1530C31C}
Browsing is NOT active on domain. Status : 6118
Master name cannot be determined from GetAdapterStatus.
4. Error from the event log:
Event Type: Error
Event Source: Server
Event ID: 2505
Description:
The server could not bind to the transport \Device\NetBT_Tcpip_{E57CCD50-5575-4191-B19A-4D1C8083D98A} because another computer on the network has the same name. The server could not start.
5. Event Type: Warning
Event Source: MRxSmb
Event ID: 3033
Description:
The redirector was unable to register the address for transport NetBT_Tcpip_{E57CCD50-5575-4191-B19A-4D1C8083D98A} for the following reason: You were not connected because a duplicate name exists on the network. Go to System in Control Panel to change the computer name and try again. . Transport has been taken offline.
This problem typically caused by RAS running on a domain controller with DNS and WINS running it.
http://support.microsoft.com/kb/292822
Other reference articles:
http://support.microsoft.com/kb/135404
http://support.microsoft.com/default.aspx?scid=kb;en-us;818092
1. Got error when run netdiag on a DC:
DC list test . . . . . . . . . . . : Failed
Failed to enumerate DCs by using the browser. [ERROR_NO_BROWSER_SERVERS_
FOUND]
2. Got "conflict" netbios info when run "nbtstat -n
3. Got error when run "browstat status":
Status for domain LGSYDNEY on transport \Device\NetBT_Tcpip_{6F7C3E8B-4519-4BA6-
AF4B-B4BB15621181}
Browsing is NOT active on domain. Status : 6118
Master browser name is held by: SSFILE01
Master browser is running build 3790
Status for domain LGSYDNEY on transport \Device\NetBT_Tcpip_{1DB6AA0C-F123-4B47-
9B57-E2DC1530C31C}
Browsing is NOT active on domain. Status : 6118
Master name cannot be determined from GetAdapterStatus.
4. Error from the event log:
Event Type: Error
Event Source: Server
Event ID: 2505
Description:
The server could not bind to the transport \Device\NetBT_Tcpip_{E57CCD50-5575-4191-B19A-4D1C8083D98A} because another computer on the network has the same name. The server could not start.
5. Event Type: Warning
Event Source: MRxSmb
Event ID: 3033
Description:
The redirector was unable to register the address for transport NetBT_Tcpip_{E57CCD50-5575-4191-B19A-4D1C8083D98A} for the following reason: You were not connected because a duplicate name exists on the network. Go to System in Control Panel to change the computer name and try again. . Transport has been taken offline.
This problem typically caused by RAS running on a domain controller with DNS and WINS running it.
http://support.microsoft.com/kb/292822
Other reference articles:
http://support.microsoft.com/kb/135404
http://support.microsoft.com/default.aspx?scid=kb;en-us;818092
2008-11-05
Troubleshooting Kerberos Authentication problems – Name resolution issues
Troubleshooting Kerberos Authentication problems – Name resolution issues
http://blogs.technet.com/askds/archive/2008/05/14/troubleshooting-kerberos-authentication-problems-name-resolution-issues.aspx
http://blogs.technet.com/askds/archive/2008/05/14/troubleshooting-kerberos-authentication-problems-name-resolution-issues.aspx
PPTP VPN tracing
Problem: user cannot connect to the PPTP VPN server. Error message showing in system log of the VPN server:
"The user hasconnected and failed to authenticate on port VPN3-127. The line has beendisconnected."
Troubleshooting:
To enable RAS tracing on the VPN server: run " netsh ras set tr * en"It will create a new folder: c:\windows\tracing
Then check the iassam log file from %windir%\tracing folder
To disable RAS tracing : netsh ras set tr * di
2008-10-01
Installaing SATA driver for HP laptop
Recently I am having problem to install SATA driver on HP 6710b laptop during SCCM deployment.
I have found this post very informative:
http://forums12.itrc.hp.com/service/forums/bizsupport/questionanswer.do?admit=109447627+1222841452430+28353475&threadId=1057792
A new HP White Paper on SATA issues:
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00765791/c00765791.pdf
I have found this post very informative:
http://forums12.itrc.hp.com/service/forums/bizsupport/questionanswer.do?admit=109447627+1222841452430+28353475&threadId=1057792
A new HP White Paper on SATA issues:
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00765791/c00765791.pdf
2008-09-30
troubleshoot PXE problem
Check the SMSTS.log for following:
Network Access Account Not Set
Resolution: Go into the Client Policy in SCCM and set a Network Access Account. It sometimes "disappears" even after everything has been working fine.
http://www.myitforum.com/forums/m_177370/mpage_1/key_/tm.htm#177370
PXE CERT Not Set
Resolution: Check the PXE Certificate in the SCCM console. Verify that the Root CA is trusted. Alternatively, reset the expiration date.
http://www.myitforum.com/forums/m_177312/mpage_1/key_/tm.htm#177312
GetHostByName Failed
Resolution: Ensure the FQDN is properly set.
http://www.myitforum.com/forums/m_177318/mpage_1/key_/tm.htm#177318
Network Access Account Not Set
Resolution: Go into the Client Policy in SCCM and set a Network Access Account. It sometimes "disappears" even after everything has been working fine.
http://www.myitforum.com/forums/m_177370/mpage_1/key_/tm.htm#177370
PXE CERT Not Set
Resolution: Check the PXE Certificate in the SCCM console. Verify that the Root CA is trusted. Alternatively, reset the expiration date.
http://www.myitforum.com/forums/m_177312/mpage_1/key_/tm.htm#177312
GetHostByName Failed
Resolution: Ensure the FQDN is properly set.
http://www.myitforum.com/forums/m_177318/mpage_1/key_/tm.htm#177318
Subscribe to:
Posts (Atom)
Posts
