![]() I decided to spend much of the morning catching up on email that’s been sent to the address. I had two meetings cancel, so I am free for the day. It would be great if I could just use Windows PowerShell for troubleshooting and not incur the overhead involved in remoting an entire desktop. Luckily, Windows always seems to prompt before anything disastrous happens-like dropping a table from a SQL database or deleting all of the events from the Security event log. There have been times when I have actually clicked the wrong item in a management tool because the screen updates were coming so slowly. Although Remote Desktop is great when connected at LAN speeds, it is not so great for accessing a heavily loaded server via a can and string WAN. This is especially true in the late afternoon when the applications update our central servers with the day’s transactions. The problem is that many of our remote offices have absolutely terrible bandwidth. In the past, we have always configured Remote Desktop on our servers to allow for remote management. ![]() Hey, Scripting Guy! I need to troubleshoot remote systems. Summary: Learn how to use Windows PowerShell troubleshooting packs to diagnose and correct problems with remote systems. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |