jlopez - Wed, 2014-05-14 18:45
I'm running Windows 8.1 on my development machine and I made the mistake of connecting to it *once* with Splashtop. Doing so turned on all of the "Touch Enabled" parts of the UI (which I can't use day to day, because the machine isn't touch enabled). The strangest of the side effects is that the menus suddenly were flush right instead of the normal US English flush left.
jlopez - Mon, 2014-03-31 12:23
This is probably the simplest solution to a confoundingly hard to pinpoint problem yet. We had some HyperV virtual machines that are managed via RDP (which is very common). For some reason the sessions would disconnect at random seeming intervals. Sometimes almost immediately, sometimes after fifteen minutes or even longer.
Many searches of the Internet and Microsoft documentation came up with nothing of real value until we stumbled across the registry key HKLM\System\CurrentControlSet\Control\Terminal\fDenyTSConnections which was set to 1.
jlopez - Mon, 2013-09-09 14:25
Although NTttcp has been around for many years, it is overlooked despite being updated to work with modern equipment (such as 10Gbps connections). Establishing your networks baseline parameters is important when diagnosing network problems: reports of a slow network are subjective and can depend on many factors.
Use in the basic testing sense is easy. Two machines will be involved, the target, which is launched from the command line as (note that you should allow ntttcp through your filewall before running)
jlopez - Mon, 2013-09-09 13:53
Over time any computer will end up with multiple copies of the same file. After adopting Dropbox to backup files between multiple computers and share files with others, it became clear that more and more duplicates were accumulating in that system, which is wasteful of the space allocated.
jlopez - Thu, 2013-04-18 09:24
Reports are rolling in that the expected 7% downturn in PC sales has turned into double that: 14% lost year or year sales. (1) The finger for the extra 7% loss is being pointed squarely at Microsoft's Windows 8.
jlopez - Fri, 2012-06-08 13:04
To add firewall rules to a remote machine allowing remote event viewing quickly, here is a batch file:
set /P INPUT=Type machine: %=%
"C:\Users\administrator.UCIA\Desktop\Sysinternals Suite\psexec.exe" \\%INPUT% ^
netsh advfirewall firewall set rule group="Remote Event Log Management" new enable=yes
From http://dbastas.blogspot.com/2009/06/configuring-firewall-for-remote.html some example groups are
jlopez - Fri, 2012-06-08 12:38
Windows 2008 R2 and other newer Microsoft operating systems are enforcing very strict permissions over C:\Windows and its sub-directories. This is a good thing as far as system security goes, but it is important to be able to modify some of these files from time to time.
In the specific case I had, I needed to made a change to %systemroot%\inf\sceregvl.inf to add rules to the group policy editor relating to remote event viewer permissions. The file was "read/execute" only to the Administrator and the Administrator's group.
jlopez - Mon, 2011-08-29 10:26
In every company there is more demand for applications than there is ability to create those applications. In the past, a workgroup in a Microsoft shop might create their own workarounds the limits of IT resources by using tools such as Microsoft Excel, Access or even a little bit of VB.NET code.
Excel is great for simple reporting, charting and even light data tracking as a intermediate step before the main line of business applications. However it quickly runs against the wall if the data being worked with is more complex than a few tables and look-ups.
jlopez - Wed, 2011-08-24 09:32
Previously we talked about the fact that the backups created by the Vista, Windows 7 and Windows Server 2008 backup tool are actually virtual hard drives which can be mounted for access via drive letters. It is also possible to mount shadow copies as well, as documented at http://blogs.msdn.com/b/adioltean/archive/2005/01/20/357836.aspx
jlopez - Wed, 2011-07-27 16:57
I had a machine with slow response in Remote Desktop. I found this article, but the primary solution was regarding Windows Vista/7 automatic configuration.
However, in the comments I found the following sequence, which does seem to reset troubled adapters even on XP:
netsh winsock reset
netsh int ip reset
netsh interface ip delete arpcache
netsh winsock reset catalog
netsh int ip reset reset.log