errorlog 直接砍了.
應該是會自動產生.
砍 不掉 service 停掉 再砍
好
你是對的
後來又發生,是有個服務出問題造成的,先停用.服務
2010/04/30
2010/04/09
Hyper-V 實體硬碟
Hyper-V 新增硬碟可以是虛擬硬碟或者是實體硬碟，若使用實體硬碟，這個實體硬碟必須在Host主機為離線硬碟。
今天測試將實體硬碟在虛擬機器卸離之後，再到Host來進行連線，仍可以看見硬碟裡面的資料。
今天測試將實體硬碟在虛擬機器卸離之後，再到Host來進行連線，仍可以看見硬碟裡面的資料。
2010/03/25
ocs 參考資料
http://blogs.technet.com/ucedsg/archive/2009/01/20/what-do-i-need-to-prepare-for-to-deploy-ocs-r2.aspx
What do I need to prepare for to deploy OCS R2?
With R2 on the horizon (Feb. 3rd), I figured you should know about some of the things to prepare for deploying R2.Run the OCS Best Practice Analyzer
If you have OCS 2007 today, you should run the OCS BPA to get a snapshot of your OCS environment. Fix any issues identified prior to rolling out R2 to help ensure a smoother transition to R2.
Do you have any 64-bit domain controllers?
If the answer is yes, you will have an easier time with OCS R2 prep work as well as with any Exchange 2007 installation.
If the answer is no, you may consider installing a 64-bit DC/GC since you can consolidate more DCs and the ratios of DC/GCs for things like Exchange improve (1 DC:8 cores of Exchange mailbox vs 1:4 with 32-bit DCs).
The OCS R2 Prep wizard only preps 64-bit Domain controllers so if you have 32-bit DCs you will need to run the command line LDIFDE tool to modify the schema from the command line.
Sample LDIFDE run on a 32-bit DC:
ldifde –i –v –k –s DC1 –f schema.ldf –c DC=X “DC=contoso,DC=com” –b Administrator password
What flavors of Active Directory work with OCS R2?
· All global catalog servers in the forest where you deploy Office Communications Server run Windows Server 2003 with SP1, Windows Server 2003 R2, or Windows Server 2008.
· All domains in which you deploy Office Communications Server are raised to a domain functional level of Windows Server 2003 or Windows Server 2008. You cannot deploy Office Communications Server 2007 R2 in a Microsoft Windows 2000 mixed, Windows 2000 native, or Windows 2003 interim domain.
· The forest in which you deploy Office Communications Server is raised to a forest functional level of Windows Server 2003 or Windows Server 2008. You cannot deploy Office Communications Server 2007 R2 in a Windows 2000 mixed, Windows 2000 native, or Windows 2003 interim forest.
Prep the Schema
R2 requires an AD schema extension so you, or someone with rights, will need schema administrator rights to deploy R2. Obviously, this is something that needs to be planned, approved, etc.
Run the R2 schema prep off hours as any schema modification forces a full global catalog replication (e.g. a 1GB DIT file means 1GB of AD data replicated across all GCs in your environment).
Prep the Forest
You also need to Forest prep to create the global settings and universal groups specific to OCS R2. This requires Enterprise admin rights to perform.
Prep the Domain
Finally, for each domain where you will host OCS users you will need to prepare the AD domain to configure OCS rights, etc. This requires domain admin rights to perform.
What else?
You should certainly be thinking about consolidated Edge and Front End architectures for most roles in addition to other functionality you may have to plan for such as Group Chat server, audio conferencing, response groups, etc.
Note: Some of this information was taken from the upcoming OCS R2 Deployment whitepaper.
In my next blog, I will talk about how to get from OCS RTM to OCS R2.
Published Tuesday, January 20, 2009 11:06 PM by markga Filed under: OCS, R2, deployment, schema
OCS 2007 R2 Schema prepare
Running Active Directory Preparation Tasks on 32-bit Domain Controllers
If you need to extend the Active Directory schema on a domain controller running a 32-bit operating system, or if you need to run the schema preparation step on a domain controller that is not the schema master, you can use the Ldifde.exe tool to import the schema file. The Ldifde.exe tool comes with most versions of the Windows operating system.
http://technet.microsoft.com/en-us/library/dd441329%28office.13%29.aspx
同事問我如何在child domain prepare exchange server schema
我原來以為這個是for exchange的，結果不是，真是年紀大了
這個是給OCS 2007r2用的，上次在客戶那裡遇到的問題也是這個OCS2007 prepare.
If you need to extend the Active Directory schema on a domain controller running a 32-bit operating system, or if you need to run the schema preparation step on a domain controller that is not the schema master, you can use the Ldifde.exe tool to import the schema file. The Ldifde.exe tool comes with most versions of the Windows operating system.
http://technet.microsoft.com/en-us/library/dd441329%28office.13%29.aspx
同事問我如何在child domain prepare exchange server schema
我原來以為這個是for exchange的，結果不是，真是年紀大了
這個是給OCS 2007r2用的，上次在客戶那裡遇到的問題也是這個OCS2007 prepare.
2010/03/12
2009/04/27
Improving TS Gateway availability using NLB
here
Recommendations about NLB parameters for TS Gateway farm scenario:
Cluster operation mode (multicast / unicast): If the gateway servers have multiple network adapters, use unicast cluster operation mode. It is a requirement that the TS Gateway farm can communicate between gateway servers. So if you have only a single NIC on gateway servers, then multicast should be used to enable communication between gateway servers in the cluster.
IP Affinity: In most cases, especially when clients originate from many different locations on the internet, like their homes, set the IP affinity to Single. There is one scenario where the IP affinity must be set to None: if many of the TS Gateway clients are behind NAT devices causing all connections to end up with the same IP and hence the same TS Gateway server, then IP affinity set to Single on NLB will load one server more than another (for example, all remote workers in a branch behind a NAT with a single external IP). In this scenario IP affinity should be set to None.
It is recommended to configure TS Gateway for a farm scenario, no matter what affinity is used. This allows users to connect in the situation where the 2 SSL connections (RPC_IN_DATA, RPC_OUT_DATA channels) originate from different client IP addresses. For example, suppose a client is trying to connect from within an organization having two proxies to the Internet (or a proxy having two Internet IP addresses) which are used randomly. In this scenario, If TS Gateway farm is not configured then the connection might fail for any NLB IP Affinity setting because SSL connections (RPC_IN_DATA, RPC_OUT_DATA) from the client may go to different TS Gateway servers.
2009/03/02
NLB相關的文件
Deployment Options for Hub Transport Servers
NLB Fundamentals
Hub transport and CAS combined role & Network load balancing
Checklist: Enabling and configuring Network Load Balancing
How To Set Up TCP/IP for Network Load Balancing in Windows Server 2003
How-To: Configure Network Load Balancing (NLB) with Two Network Adapters
如何設定網路負載平衡參數在 Windows Server 2003 中
2008/01/03
2008/01/02
Microsoft Virtual Server support policy
Microsoft Virtual Server support policy
http://support.microsoft.com/kb/897613/
http://support.microsoft.com/kb/897613/
2007/12/26
如何藉由使用 ISA Server 封鎖 MSN Messenger 傳輸及 Live Windows Messenger 傳輸"
Andy's Share: 如何藉由使用 ISA Server 封鎖 MSN Messenger 傳輸及 Live Windows Messenger 傳輸: "如何藉由使用 ISA Server 封鎖 MSN Messenger 傳輸及 Live Windows Messenger 傳輸"
KB:925120
KB:925120
2007/12/17
Description of System Center Essentials 2007 post-release hotfix rollup
Description of System Center Essentials 2007 post-release hotfix rollup
The Microsoft System Center Essentials 2007 post-release hotfix rollup is available.
The Microsoft System Center Essentials 2007 post-release hotfix rollup is available.
2007/12/10
2007/12/07
以管理為優先的Windows Server 2003 R2（上）
以管理為優先的Windows Server 2003 R2（上）
Microsoft Services for NFS的前身是Services for UNIX 3.5，但更新後的Microsoft Services for NFS還具有下列新功能：
•x64 位元的支援：Microsoft Services for NFS可安裝在Windows Server 2003 R2的所有版本上，包括x64位元版本。
•更新的Microsoft Services for NFS Administration，這是MMC嵌入式管理單元，讓管理者能以圖形介面工具管理NFS。
•更穩定的可靠性
•支援特殊的UNIX裝置（mknod）
Microsoft Services for NFS允許UNIX用戶端存取Windows Server 2003 R2上的資源。企業或組織內若有UNIX檔案伺服器和UNIX用戶端，而且UNIX用戶端可存取UNIX檔案伺服器裡的檔案資源，若要充分利用Windows Server 2003 R2的功能（例如共用資料夾的陰影複製），可以將UNIX檔案伺服器上的資源，移至Windows Server 2003 R2伺服器，然後設定Microsoft Services for NFS，以啟用執行NFS軟體的UNIX用戶端存取權，如此一來，所有UNIX用戶端都不需要進行任何變更，就可以透過NFS通訊協定存取移至Windows Server 2003 R2伺服器的檔案資源。
此外，Microsoft Services for NFS也可以讓Windows Server 2003 R2伺服器存取UNIX檔案伺服器上的資源。例如混用Windows與UNIX的環境，可能會有資源（例如檔案）存放在UNIX檔案伺服器，若UNIX檔案伺服器也使用NFS，就可以使用Microsoft Services for NFS讓Windows Server 2003 R2伺服器存取UNIX伺服器上的資源。
Microsoft Services for NFS的前身是Services for UNIX 3.5，但更新後的Microsoft Services for NFS還具有下列新功能：
•x64 位元的支援：Microsoft Services for NFS可安裝在Windows Server 2003 R2的所有版本上，包括x64位元版本。
•更新的Microsoft Services for NFS Administration，這是MMC嵌入式管理單元，讓管理者能以圖形介面工具管理NFS。
•更穩定的可靠性
•支援特殊的UNIX裝置（mknod）
Microsoft Services for NFS允許UNIX用戶端存取Windows Server 2003 R2上的資源。企業或組織內若有UNIX檔案伺服器和UNIX用戶端，而且UNIX用戶端可存取UNIX檔案伺服器裡的檔案資源，若要充分利用Windows Server 2003 R2的功能（例如共用資料夾的陰影複製），可以將UNIX檔案伺服器上的資源，移至Windows Server 2003 R2伺服器，然後設定Microsoft Services for NFS，以啟用執行NFS軟體的UNIX用戶端存取權，如此一來，所有UNIX用戶端都不需要進行任何變更，就可以透過NFS通訊協定存取移至Windows Server 2003 R2伺服器的檔案資源。
此外，Microsoft Services for NFS也可以讓Windows Server 2003 R2伺服器存取UNIX檔案伺服器上的資源。例如混用Windows與UNIX的環境，可能會有資源（例如檔案）存放在UNIX檔案伺服器，若UNIX檔案伺服器也使用NFS，就可以使用Microsoft Services for NFS讓Windows Server 2003 R2伺服器存取UNIX伺服器上的資源。
XADM: Notifying Exchange and Outlook Clients of Password Expiration
XADM: Notifying Exchange and Outlook Clients of Password Expiration: "Password Expiration Warning Application "
訂閱：
文章 (Atom)