Windows 服務器系列:
- Windows:查看IP地址,IP地址對應的機器名,占用的端口,以及占用該端口的應用程
- Windows:使用Dos命令管理服務(Services)
- Windows:任務調度器
- Windows:打開MSDTC,恢復Windows任務欄,查看windows日志,打開遠程桌面,打開Services,資源監控
一,Win10 打開 MSDTC
1,Win+R 打開運行窗口,輸入 dcomcnfg,打開組件服務窗口
2,在組件服務 catalog下找到 Distributed Transaction Coordinator下的本地DTC
3,打開本地DTC的屬性,設置安全tab,選中“網絡DTC訪問”,勾選“允許遠程客戶端”,“允許遠程管理”,“允許入站”,“允許出站”,“要求相互進行身份驗證”,DTC登陸賬戶為:NT Authority\Network Service
二,恢復Windows TaskBar
1,Task bar 如下圖,使用Windows OS的用戶可能會遇到Task Bar 不見的情況
2,解決方法
Ctrl+Alt+Delete 打開 Task Manager,在File菜單中,選擇“Run new task”,輸入 explorer.exe,執行這個命令即可
三,查看windows日志
Windows Logs 集成在Event Viewer中,可以通過兩種方式打開
1,通過Manage打開Windows Logs
打開路徑:Computer->Manage->System tools
2,通過管理工具打開Event Viewer
打開路徑:Control Panel->Admin Tools->Event Viewer,在Event Viewer中能夠打開Windows Logs
四,打開Remote Desktop Connection
1,點擊Win+R 打開運行窗口,輸入 mstsc,打開
2,管理計算器的憑證(Credential Manager)
通過控制面板打開憑證管理:Control Panel->Credential Manager
點擊windows Credentials,能夠管理Remote Desktop Connection 使用的Windows憑證,存儲這些憑證,在遠程連接桌面時,只需要選擇Server name,復雜的密碼就會以暗文方式自動輸入,無需記憶復雜的密碼。
五,打開Services
1,通過命令打開Service窗口
點擊Win+R 打開運行窗口,輸入 services.msc,打開Services
2,刪除已經安裝的Service
在Dos命令行窗口中,使用命令刪除service
su delete service-name
六,打開資源監控器(Resource Monitor)
Resource Monitor 是Real-Time 監控 CPU,Memory,Disk 和 Network 資源的Monitor
1,按住“Windows+R”打開命令行窗口,輸入命令“resmon”,打開資源監視器
2,選擇性監控Resource Usage
在應用程序列表中勾擇 sqlservr.exe,實時查看SQL Server的資源使用情況。
附件: Memory Tab
- Memory:Memory displays the current hard faults per second in green and displays the percentage of physical memory currently in use in blue.
- Image: The application that is using memory resources.
- PID: The process ID of the application instance.
- Hard Faults/min: The number of hard faults per minute that are currently resulting from the application instance.
- Working set (KB): The number of kilobytes of the application instance working set that may be available for other applications to use.
- Private (KB): The number of kilobytes of the application instance working set that is dedicated to the process.
A hard fault (also known as a page fault) occurs when the page of the referenced address is no longer in physical memory and has been swapped out or is available from a backing file on disk. It is not an error. However, a high number of hard faults may explain the slow response time of an application if it must continually read data back from disk rather than from physical memory.