Search Results

Search found 6 results on 1 pages for 'gomibushi'.

Page 1/1 | 1 

• How do I remove the on screen keyboard from the logon screen in Windows Remote Desktop Server 2008 R

  - by Gomibushi

  The on screen keyboard (OSK) from the "ease of access" tools pops up on EVERY connect to the server, even if you have not activated it. I can't seem to find a control panel or reg setting to switch it off. It is VERY "in your face" for linux users who connect at lower resolutions and do not provide all credentials, but have to type username and password. I'm running a 2008 R2 Terminal Server/Remote Desktop Server.

  Read the article

• Client backup solution for small (100-150 user) homogenous win/nix/mac office?

  - by Gomibushi

  We are currently using Symantec Backup Exec with Desktop and Laptop Option for our Windows clients, time machine for mac and offer simple rsync to linux users, in addition to home folders that are always backed up and available. We are not overly happy with the horrid complexity and multitude of minor bugs in SBE, but "when you don't touch it, it mostly works". Ideally we'd like to offer a real and full backup solution to all clients, but mostly to Linux users, as they don't have a good alternative. I have barely tested Druva on windows, and it is promising in its simplicity and "it just works" looks, but does anyone have experience with it? This post lists some that I will look at.

  Read the article

• Windows/Samba connection error

  - by Gomibushi

  I have a Linux fileserver serving up /home for linux and windows users. I was able to connect from my windows client, but not from a DC. Then suddenly I could connect from the DC too. The linux servers run Centrify clients, and as such are part of the domain. All on same subnet. This is what the the log.smbd says, repeatedly: [2010/02/11 11:25:57, 0] lib/util_sock.c:read_data(534) read_data: read failure for 4 bytes to client 192.168.200.3. Error = Connection reset by peer On Windows it appeared as an "unknown error". EDIT: the error code is "0x80004005". We are developing a system depended on the samba share, and are worried this will appear again. It would be nice to pin point the root of this. Any ideas what this might be? Places to look?

  Read the article

• Install a program from the network

  - by Gomibushi

  In Windows there is a place under the Control Panel called Get Programs and Install a program from the network (in Win 7 at least), possibly a slightly different name in Vista, but it was there too. The question is basically: How do you publish programs to that so users can go there and install? Bonus follow up: Is it a good way to deploy optional programs? (Compared to using GPO's.) In Windows 7 you can go to Control Panel, Programs, Programs and Features, and on the left hand menu: Install a program from the network.

  Read the article

• What do you do with a 15 node decommissioned Itanium cluster?

  - by Gomibushi

  We are decommissioning a 15 node Itanium cluster. We don't know what to do with it. Being geeks we want to put it (or its individual nodes) to some cool use, but since it is Itanium we are a bit unsure what that could/would be. We are not bringing it back as production servers and we are considering giving them away, if anyone wants them. It's not the most spiffy hardware, but being 2U rack servers they pack an ok amount of cpu and memory, they're about 3 years old perhaps. Ideas to what runs well on them? Or something one can use them as?

  Read the article

• Windows/Samba connection error

  - by Gomibushi

  I have a Linux fileserver serving up /home for linux and windows users. I was able to connect from my windows client, but not from a DC. Then suddenly I could connect from the DC too. The linux servers run Centrify clients, and as such are part of the domain. All on same subnet. This is what the the log.smbd says, repeatedly: [2010/02/11 11:25:57, 0] lib/util_sock.c:read_data(534) read_data: read failure for 4 bytes to client 192.168.200.3. Error = Connection reset by peer On Windows it appeared as an "unknown error". EDIT: the error code is "0x80004005". We are developing a system depended on the samba share, and are worried this will appear again. It would be nice to pin point the root of this. Any ideas what this might be? Places to look?

  Read the article

1