Disable the “Disconnect” button

When a user connects to Windows XP desktops through Terminal Service {RDP, Citrix Xen}. By default, they are able to disconnect from the desktop. By disconnect, the terminal session remains open on the terminal host. This issue is driving me nuts at work, because when users try to connect again, Xen DDC doesn’t seem to deliver their last (opened) session. Instead, it trys to give them a new one.

Terminal Services Disconnect Button

It makes me want to cry, because we’ve specifically told users to log off instead of disconnect.

Sure, there are a few group policies you can modify to kill disconnected sessions. But I want to let users know, I don’t want them to disconnect! Period…

Disable the Disconnect button should do it, this policy is under Administrative Template > Windows Component > Terminal Services. It can be applied in the Group Policy on the VHD itself, or through the GPO on your domain controller. Enough said… I hate id10t users.

TIPS: WINDOWS PRINTER ISSUES

Here are my tips to the “Senior Tech Wannabe” about windows printer trouble shooting.

Problem: “I selected the printer, and hit the delete key a few times. But it doesn’t delete, though the status says deleting.”
Answer: “Cancel all the unfinished documents in the queue first. Damn it!”

Problem: “I cannot cancel or restart a job in the print queue. It’s just stuck!”
Answer: “Right click on My Computer > Manage > Services and Applications > Services > Right click on Print Spooler > Restart.”

NO SHOUTING IN THE DATACENTER, PLEASE!

Don't shout at your disks!

Check this out, apparently shouting at your disks causes extreme latency. So, either keep your noises down in the datacenter, or upgrade to solid state drives! Click read more to watch the video. Read more »

Windows 7 Beta ISO leaked on torrent

Windows 7 Screenshot

The ISO appears to contain the Windows 7 M1 build (7000) highlighted by Paul Thurrott on SuperSite. So far the new build seems to perform slightly better than 6801, and memory usage has been improved. A number of previously hidden features – like the iconized task bar – are also now active.

Before comments start asking why there’s no link to the file, it’s because this is something that we’re not supposed to have yet. If you want to get your hands on it, check your favorite torrent search site. Also keep in mind that this is a leak, and there’s always the possibility that the ISO has been tampered with.

via Windows 7 Beta ISO leaked on torrent trackers – Download Squad.

Did you know? Free Anti-Virus Software.

Edit: AT&T now provides McAfee too.

Stupid viruses and worms are spreading like crazy. They are almost impossible to avoid or spot while we surf and download. But did you know most ISPs provides FREE Anti-Virus along with your service subscription?

Here in the Bay Area, 2 of the major Internet Service Providers are AT&T and Comcast. You can login to the member services website to download your copy of the software. AT&T gives you Symantec Secuirty Suite while Comcast offers the McAfee Security Center. They are the full suite including Anti-Virus, Firewall and Spyware cleaner. Each worth more than $100 if purchased from a retail store.

In order to download, you might have to login using the master account.

Pic of the day: Hard Working Guy

I admire hard working people, specially when they have to deploy a hundred PCs in a day.

Disable Windows Firewall Remotely

Being domain administrator in a complex network, you don’t want to walk around to fix issues or to install a software. You rely on remote desktop solutions to get into other devices. I use the admin share (\\node\x$) command very often. However, when the devices you’re working with has Windows firewall enabled, you’re out of luck. 

Turning off Windows firewall remotely seems to be impossible in enterprise networks. Of course, in a network with 20 desktops, you could just simply walk over and do it. I’ve done a lot of searches and tried various of methods, the conclusion is: No Go!

A guy once wrote an au3 script, some people confirmed it works. But when I tired it recently, it works only if the target client is yourself. When I tried the script targeting another node, it does nothing. The way I see it: If windows firewall blocks incoming ICMP packets, it’s pretty much it. I have to walk over to the node and manually turn WFW off.

Maybe, creating a global policy on the domain controller would be the way to go…

« Previous PageNext Page »