2010/12/31
Downloads | Remote Administration For Windows
Downloads | Remote Administration For Windows: "- 已使用 Google 工具列寄出"
A Networker's Log File: Migrating KMS Host for Windows Activation
A Networker's Log File: Migrating KMS Host for Windows Activation: "
Two types of activation for Microsoft OS, MAK (Multiple Activation Key) and KMS (Key Management Service). The former activation is mainly used for less than 5 servers. If you use KMS, the first four hosts won't be activated until the fifth is activated. Earlier, we did a mistake of keying in the KMS host license key into some of our servers instead of the KMS client keys. As a result, multiple SRV of _VLMCS._tcp. appears on the DNS servers. Furthermore, the current KMS server is not supposed to have Internet access. Hence, we decided to migrate the KMS to another VM.
- 已使用 Google 工具列寄出"
Two types of activation for Microsoft OS, MAK (Multiple Activation Key) and KMS (Key Management Service). The former activation is mainly used for less than 5 servers. If you use KMS, the first four hosts won't be activated until the fifth is activated. Earlier, we did a mistake of keying in the KMS host license key into some of our servers instead of the KMS client keys. As a result, multiple SRV of _VLMCS._tcp. appears on the DNS servers. Furthermore, the current KMS server is not supposed to have Internet access. Hence, we decided to migrate the KMS to another VM.
- 已使用 Google 工具列寄出"
KMS Client Setup Keys
KMS Client Setup Keys:
"By default, the Windows 7 and Windows Server 2008 R2 operating systems use KMS for activation. In volume installations, the setup key is installed by default, which makes the system a KMS client. If you are converting a computer from a KMS host, MAK, or retail edition of Windows to a KMS client, install the applicable setup key (GVLK) from Table 9 using slmgr /ipk .
- 已使用 Google 工具列寄出"
"By default, the Windows 7 and Windows Server 2008 R2 operating systems use KMS for activation. In volume installations, the setup key is installed by default, which makes the system a KMS client. If you are converting a computer from a KMS host, MAK, or retail edition of Windows to a KMS client, install the applicable setup key (GVLK) from Table 9 using slmgr /ipk .
- 已使用 Google 工具列寄出"
KMS on Windows Server 2008 R2 (Network Steve Forum)
KMS on Windows Server 2008 R2 (Network Steve Forum): "KMS on Windows Server 2008 R2
- 已使用 Google 工具列寄出"
- 已使用 Google 工具列寄出"
Count KMS Activation (Network Steve Forum)
Count KMS Activation (Network Steve Forum): "- 已使用 Google 工具列寄出"
Configuring KMS Hosts
Configuring KMS Hosts:
Table 1 Slmgr.vbs Parameters
/sprt PortNumber
Sets the TCP communications port on a KMS host. Replace PortNumber with the TCP port number to use. The default setting is 1688.
/cdns
Disables automatic DNS publishing by a KMS host.
/sdns
Enables automatic DNS publishing by the KMS host.
/cpri
Lowers the priority of KMS host processes.
/spri
Sets the priority of KMS host processes to Normal.
/sai ActivationInterval
Changes how often a KMS client attempts to activate itself when it cannot find a KMS host. Replace ActivationInterval with a number of minutes. The default setting is 120.
/sri RenewalInterval
Changes how often a KMS client attempts to renew its activation by contacting a KMS host. Replace RenewalInterval with a number of minutes. The default setting is 10080 (7 days). This setting overrides the local KMS client settings.
/dli
Retrieves the current KMS activation count from the KMS host.
- 已使用 Google 工具列寄出"
Table 1 Slmgr.vbs Parameters
/sprt PortNumber
Sets the TCP communications port on a KMS host. Replace PortNumber with the TCP port number to use. The default setting is 1688.
/cdns
Disables automatic DNS publishing by a KMS host.
/sdns
Enables automatic DNS publishing by the KMS host.
/cpri
Lowers the priority of KMS host processes.
/spri
Sets the priority of KMS host processes to Normal.
/sai ActivationInterval
Changes how often a KMS client attempts to activate itself when it cannot find a KMS host. Replace ActivationInterval with a number of minutes. The default setting is 120.
/sri RenewalInterval
Changes how often a KMS client attempts to renew its activation by contacting a KMS host. Replace RenewalInterval with a number of minutes. The default setting is 10080 (7 days). This setting overrides the local KMS client settings.
/dli
Retrieves the current KMS activation count from the KMS host.
- 已使用 Google 工具列寄出"
Configuring KMS Clients
Configuring KMS Clients:
"Enable Auto-discovery for a KMS Client
By default, KMS clients automatically attempt to discover KMS hosts. Auto-discovery can be disabled by manually assigning a KMS host to a KMS client. This action also clears the KMS host name from the KMS client’s cache. If auto-discovery is disabled, it can be re-enable by running slmgr.vbs /ckms at a command prompt.
- 已使用 Google 工具列寄出"
"Enable Auto-discovery for a KMS Client
By default, KMS clients automatically attempt to discover KMS hosts. Auto-discovery can be disabled by manually assigning a KMS host to a KMS client. This action also clears the KMS host name from the KMS client’s cache. If auto-discovery is disabled, it can be re-enable by running slmgr.vbs /ckms at a command prompt.
- 已使用 Google 工具列寄出"
slmgr.vbs 完整用法 - 小胡's Blog - 漫步人生，总是舍不得，放不下，珍惜一切
slmgr.vbs 完整用法 - 小胡's Blog - 漫步人生，总是舍不得，放不下，珍惜一切: "Windows 软件授权管理工具(slmgr.vbs)完整用法
计算机名: 远程计算机的名称(默认为本地计算机)
用户: 远程计算机上具有所需特权的帐户
密码: 帐户的密码
可用选项:
-ipk
安装产品密钥(替换现有密钥)
-upk
卸载产品密钥
-ato
激活 Windows
-dli [激活 ID | All]
显示许可证信息(默认: 当前许可证)
-dlv [激活 ID | All]
显示详细的许可证信息(默认: 当前许可证)
-xpr
当前许可证状态的截止日期
- 已使用 Google 工具列寄出"
计算机名: 远程计算机的名称(默认为本地计算机)
用户: 远程计算机上具有所需特权的帐户
密码: 帐户的密码
可用选项:
-ipk
安装产品密钥(替换现有密钥)
-upk
卸载产品密钥
-ato
激活 Windows
-dli [激活 ID | All]
显示许可证信息(默认: 当前许可证)
-dlv [激活 ID | All]
显示详细的许可证信息(默认: 当前许可证)
-xpr
当前许可证状态的截止日期
- 已使用 Google 工具列寄出"
Moving KMS to a new box in Windows Server
Moving KMS to a new box in Windows Server: "
My understanding of KMS is that kms machines operate independently of each other, you are not moving it as such you just need to install a new machine. Clients find kms servers by querying dns and your new kms server will automatically publish its srv record. James. --
- 已使用 Google 工具列寄出"
My understanding of KMS is that kms machines operate independently of each other, you are not moving it as such you just need to install a new machine. Clients find kms servers by querying dns and your new kms server will automatically publish its srv record. James. --
- 已使用 Google 工具列寄出"
2010/12/30
Windows Server 2008 R2 maximum NTFS volume size - Operating Systems
Windows Server 2008 R2 maximum NTFS volume size - Operating Systems: "
For NTFS the default size of allocation units is 4096 bytes.
- 已使用 Google 工具列寄出"
For NTFS the default size of allocation units is 4096 bytes.
- 已使用 Google 工具列寄出"
sector size
記錄檔複製器無法繼續處理資料庫 ''，因為目標伺服器
發生錯誤: 連續複寫 - 已終止區塊模式。錯誤: the log file sector
size does not match the current volume's se
ctor size (-546) [HResult: 0x80131500].。複製器在
短暫延遲後將自動重試。
發生錯誤: 連續複寫 - 已終止區塊模式。錯誤: the log file sector
size does not match the current volume's se
ctor size (-546) [HResult: 0x80131500].。複製器在
短暫延遲後將自動重試。
How can I get the cluster size on Windows 2008? - Server Fault
How can I get the cluster size on Windows 2008? - Server Fault: "Use the following command:
fsutil fsinfo ntfsinfo c: (where c: is the volume/path to obtain the data for)
This will show you smilar to the following:
NTFS Volume Serial Number : 0x9e800d87800d675d
Version : 3.1
Number Sectors : 0x000000000c7fffff
Total Clusters : 0x00000000018fffff
Free Clusters : 0x000000000091cfd1
Total Reserved : 0x00000000000001b0
Bytes Per Sector : 512
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 1024
Clusters Per FileRecord Segment : 0
Mft Valid Data Length : 0x0000000009fc0000
Mft Start Lcn : 0x00000000000c0000
Mft2 Start Lcn : 0x0000000000c7ffff
Mft Zone Start : 0x00000000000c9ca0
Mft Zone End : 0x00000000000ca7e0
RM Identifier: 07A1930B-353D-11DE-AB63-E15CC5EE82D6
- 已使用 Google 工具列寄出"
fsutil fsinfo ntfsinfo c: (where c: is the volume/path to obtain the data for)
This will show you smilar to the following:
NTFS Volume Serial Number : 0x9e800d87800d675d
Version : 3.1
Number Sectors : 0x000000000c7fffff
Total Clusters : 0x00000000018fffff
Free Clusters : 0x000000000091cfd1
Total Reserved : 0x00000000000001b0
Bytes Per Sector : 512
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 1024
Clusters Per FileRecord Segment : 0
Mft Valid Data Length : 0x0000000009fc0000
Mft Start Lcn : 0x00000000000c0000
Mft2 Start Lcn : 0x0000000000c7ffff
Mft Zone Start : 0x00000000000c9ca0
Mft Zone End : 0x00000000000ca7e0
RM Identifier: 07A1930B-353D-11DE-AB63-E15CC5EE82D6
- 已使用 Google 工具列寄出"
2010/12/29
sending & receiving sms messages using outlook 2010 or outlook web app, and windows mobile - Ilse Van Criekinge's Weblog - Site Home - TechNet Blogs
sending & receiving sms messages using outlook 2010 or outlook web app, and windows mobile - Ilse Van Criekinge's Weblog - Site Home - TechNet Blogs: "How does it work?
When a text (sms) message is created using Outlook/OWA, it will be sent to Exchange. Exchange will use EAS to send/sync the message to the users cell phone. The user’s cell phone will then send that message out over SMS.
When a user receives a text message, the sent message will be synced to the user’s mailbox using EAS.
- 已使用 Google 工具列寄出"
When a text (sms) message is created using Outlook/OWA, it will be sent to Exchange. Exchange will use EAS to send/sync the message to the users cell phone. The user’s cell phone will then send that message out over SMS.
When a user receives a text message, the sent message will be synced to the user’s mailbox using EAS.
- 已使用 Google 工具列寄出"
Outlook 2010, Windows Mobile & SMS Sync: Send and receive text messages from your e-mail account - Le Café Central de DeVa - Site Home - MSDN Blogs
Outlook 2010, Windows Mobile & SMS Sync: Send and receive text messages from your e-mail account - Le Café Central de DeVa - Site Home - MSDN Blogs: "- 已使用 Google 工具列寄出"
sending & receiving sms messages using outlook 2010 or outlook web app, and windows mobile - Ilse Van Criekinge's Weblog - Site Home - TechNet Blogs
sending & receiving sms messages using outlook 2010 or outlook web app, and windows mobile - Ilse Van Criekinge's Weblog - Site Home - TechNet Blogs: "- 已使用 Google 工具列寄出"
A while ago I got a question from someone regarding one of the new features in Exchange 2010, being text messaging. Question was “is it available”…
Looking at the TechNet article he referred to, it does state:
Source = http://technet.microsoft.com/en-us/library/dd298136.aspx
The following is a list of new text messaging features included in Exchange 2010:
- Missed call and voice mail notifications
- Calendar and agenda updates
- Text messages sent and received through Outlook Web App and Outlook 2010
- Text message synchronization with a mobile phone
So let’s see.
Requirements
You need to have a Windows Mobile device:
- Windows Mobile 6.1 + https://update.outlook.com/cabs/OutlookLiveSetup.cab
- Windows Mobile 6.5
- Exchange 2010
Text Messages (SMS) Synching with Exchange 2010 and Rule to move Text Messages (SMS) to a folder using Outlook 2010 - AVIRAJ AJGEKAR'S BLOG... - Site Home - TechNet Blogs
Text Messages (SMS) Synching with Exchange 2010 and Rule to move Text Messages (SMS) to a folder using Outlook 2010 - AVIRAJ AJGEKAR'S BLOG... - Site Home - TechNet Blogs: "- 已使用 Google 工具列寄出"
How to send/receive SMS in MS Exchange 2010
How to send/receive SMS in MS Exchange 2010: "- 已使用 Google 工具列寄出"
2010/12/27
Error message when users use an SMTP client to send e-mail messages in Exchange Server 2007 Service Pack 1: "454 4.7.0 Temporary authentication failure"
Error message when users use an SMTP client to send e-mail messages in Exchange Server 2007 Service Pack 1: "454 4.7.0 Temporary authentication failure": "- 已使用 Google 工具列寄出"
Authentication Prob between 2 hub servers - cannot send/receive.
Authentication Prob between 2 hub servers - cannot send/receive.: "- 已使用 Google 工具列寄出"
"454 4.7.0 temporary authentication failure"
"454 4.7.0 temporary authentication failure"
2010/12/22
x64? My Terminal Servers Run Just Fine With 32 Bits and 8/12/16 GB RAM! | sepago
x64? My Terminal Servers Run Just Fine With 32 Bits and 8/12/16 GB RAM! | sepago: "x64? My Terminal Servers Run Just Fine With 32 Bits and 8/12/16 GB RAM!
PAE
Windows can be booted with the /PAE option. PAE makes the kernel use 4 additional address lines which are built into (nearly) every CPU since the Pentium Pro. Modern CPUs have 36 instead of 32 address lines and support a maximum of 64 GB RAM (with PAE enabled).
But how can a traditional 32-bit application that can only count to 2^32 and that knows nothing of AWE access such "high" memory?
Easy: all the hard work is done by the operating system. Remember that each application has its private virtual address space that always ranges from 0x00000000 to 0xFFFFFFFF. But programs cannot simply access any address in that range. Doing so would result in the well-known general protection fault. Instead applications must request memory from the OS. The OS then chooses the appropriate amount of free pages (RAM is managed in units of pages with a size of 4 KB each). Finally the pages are mapped from physical RAM into the virtual memory of the requesting process.
By virtualizing the address space of processes, it has become irrelevant to applications where a page actually is located. It could have been moved to disk (to the page file, of course) to make room for other process's demands. Or it could reside in the area above 4 GB. Since applications only work with virtual addresses in the 32-bit range they need not be modified as long as they use less than 2 GB of memory.
With PAE, multiple 32-bit processes without AWE support can still only use 2 GB each. But it is perfectly possible to have 20 applications on a terminal server that each need 300 MB RAM if the machine is equipped with 8 GB (leaving room for the kernel and OS). This is because the map from virtual to physical memory is different for every process.
PAE
Windows can be booted with the /PAE option. PAE makes the kernel use 4 additional address lines which are built into (nearly) every CPU since the Pentium Pro. Modern CPUs have 36 instead of 32 address lines and support a maximum of 64 GB RAM (with PAE enabled).
But how can a traditional 32-bit application that can only count to 2^32 and that knows nothing of AWE access such "high" memory?
Easy: all the hard work is done by the operating system. Remember that each application has its private virtual address space that always ranges from 0x00000000 to 0xFFFFFFFF. But programs cannot simply access any address in that range. Doing so would result in the well-known general protection fault. Instead applications must request memory from the OS. The OS then chooses the appropriate amount of free pages (RAM is managed in units of pages with a size of 4 KB each). Finally the pages are mapped from physical RAM into the virtual memory of the requesting process.
By virtualizing the address space of processes, it has become irrelevant to applications where a page actually is located. It could have been moved to disk (to the page file, of course) to make room for other process's demands. Or it could reside in the area above 4 GB. Since applications only work with virtual addresses in the 32-bit range they need not be modified as long as they use less than 2 GB of memory.
With PAE, multiple 32-bit processes without AWE support can still only use 2 GB each. But it is perfectly possible to have 20 applications on a terminal server that each need 300 MB RAM if the machine is equipped with 8 GB (leaving room for the kernel and OS). This is because the map from virtual to physical memory is different for every process.
Physical Address Extension (Windows)
Physical Address Extension (Windows): "Enabling PAE
Windows automatically enables PAE if DEP is enabled on a computer that supports hardware-enabled DEP, or if the computer is configured for hot-add memory devices in memory ranges beyond 4 GB. If the computer does not support hardware-enabled DEP or is not configured for hot-add memory devices in memory ranges beyond 4 GB, PAE must be explicitly enabled.
To explicitly enable PAE, use the following BCDEdit /set command to set the pae boot entry option:
bcdedit /set [{ID}] pae ForceEnable
IF DEP is enabled, PAE cannot be disabled. Use the following BCDEdit /set commands to disable both DEP and PAE:
bcdedit /set [{ID}] nx AlwaysOff
bcdedit /set [{ID}] pae ForceDisable
Windows Server 2003 and Windows XP/2000: To enable PAE, use the /PAE switch in the Boot.ini file. To disable PAE, use the /NOPAE switch. To disable DEP, use the /EXECUTE switch.
- 已使用 Google 工具列寄出"
Windows automatically enables PAE if DEP is enabled on a computer that supports hardware-enabled DEP, or if the computer is configured for hot-add memory devices in memory ranges beyond 4 GB. If the computer does not support hardware-enabled DEP or is not configured for hot-add memory devices in memory ranges beyond 4 GB, PAE must be explicitly enabled.
To explicitly enable PAE, use the following BCDEdit /set command to set the pae boot entry option:
bcdedit /set [{ID}] pae ForceEnable
IF DEP is enabled, PAE cannot be disabled. Use the following BCDEdit /set commands to disable both DEP and PAE:
bcdedit /set [{ID}] nx AlwaysOff
bcdedit /set [{ID}] pae ForceDisable
Windows Server 2003 and Windows XP/2000: To enable PAE, use the /PAE switch in the Boot.ini file. To disable PAE, use the /NOPAE switch. To disable DEP, use the /EXECUTE switch.
- 已使用 Google 工具列寄出"
2010/12/10
Exchange Server 2007 and Public Folder Replicas | Aaron Parker
Exchange Server 2007 and Public Folder Replicas | Aaron Parker: "In our case I missed the SCHEDULE+ FREE BUSY folder. This resulted in Outlook 2003 clients unable to see Free/Busy information when creating a meeting request. The user would see this error in Outlook when attempting to see another users schedule:
- 已使用 Google 工具列寄出"
- 已使用 Google 工具列寄出"
2010/12/06
訂閱：
文章 (Atom)