ijk

A key skill - I don't know the answer to that question, but I can find out.

Sure, but this is a how do you do it thread. If someone is attempting to achieve a technical goal I believe it's important to focus on the technical aspects of that goal in a brain thread that is separated from the organisational aspects. If I work that way I find I get more done.

Quite. We don't provide our teachers with a school issued computer and do not use a VPN. I outlined our approach in a similar thread earlier this evening and came across this thread later. I think it's an interesting area. Briefly, we allow remote desktop connections from users personal equipment through a SSH tunnel. It works okay for us and doesn't connect their equipment to the network. I don't know how it would scale - only a handful of users have access (through desire/need rather than a sense of privilege) and it's there for a specific purpose at the moment, that of reading/approving reports twice a year. The costs involved are RDS cals, cost of Bitvise SSH server and cost of Bitvise Tunnelier client for each user (edit: plus time of course).

Where this isn't possible and users connect using their home computers, what measures do you think should be in place to protect internal networks?

We do the following: Bitvise SSH server running on a non-standard port. Single SSH user allowed to connect (multiple concurrent sessions allowed) but no shell. RDS server accepting connections, again on a non-standard port. Users are provided with a copy of Bitvise Tunnelier and a pre-configured config file, which they can use to launch the client. (We have a few Mac users who like to connect and I teach them how to create the tunnel on the terminal.) This makes the connection, asks them for a password and then launches the RDP client preconfigured to connect to the RDS server through the tunnel. They log into the RDS server with their usual credentials. It seems to work okay, but we're a very small institution with few users and I don't know how it would scale up.

Is this what you want? : http://www.tightvnc.com/doc/win/TightVNC-installer-2.5.2.pdf

How soon?

What are memory sticks going to be replaced with?

If it has an RM serial number - WOsomething - you should be able to find everything you need online at rm.com/support

Has no-one else experienced this issue? I know that many of you are using the MDT to do your deployments but the "Install Software, Make changes, Make Image" routine is ingrained. Is there anyone who is using WDS to name clients, and are using the %MAC variable in their Client Naming Policy who hasn't had this problem? ?

Hi, Server 2008 R2/WDS. I am having a problem naming clients that I auto-add to the AD by WDS. The server is configured to name clients using the %MAC variable. As I understand it that should mean that when I respond to pending clients and choose approve they should be named using their NIC's mac address. However this doesn't seem to happen and I have observed the following behaviour: 1) While the server is configured with wdsutil /set-server /prestageusingmac:no the computer account is created in AD using what looks like a randomisation of the GUID. At first I though it was the first 12 elements of the GUID, but then it appeared on closer inspection that it is randomised. I may be wrong. Nevertheless, each new client is successfully created in AD and everything runs on as expected. 2) While the server is configured with wdsutil /set-server /prestageusingmac:yes the computer account is created in AD using what, without any doubt, looks like 000000000000. This is either the first 12 units of the mac address (when using the prestageusingmac:yes option the computer's GUID is like the GUID in 1), but is e.g. 00000000-0000-0000-0000-08002B30309D, where 08002B30309D is the mac address) or a randomisation of the GUID, which has so far not managed to randomise any of the mac part of the address, thus always showing 0s. As a consequence in 2) WDS fails to name the second approved client because there is a duplicate in AD. If I configure the server client naming policy to be something like xyz%3# then approved computers are named according to that rule regardless of whether prestageusingmac is set to yes or no. I find this jolly confusing. Searching The Big Book yields a few reports and a MS hotfix for a problem that is similar to the one I think I'm experiencing (my problem may be a misconfiguration/misunderstanding). Specifically Windows Deployment Services generates duplicate client computer names when the %MAC variable is used. However I don't think that kb is describing my problem. It says in the symptoms section: "However, when WDS deploys the client computers during the unattended phase." What I am experiencing doesn't occur at that stage, it occurs when approving clients and auto-adding them to AD. At the moment I'm just going to pretend this isn't happening and either name them manually (name and approve) or use a client naming policy that works, but I'd really like to know what is happening, and where it is going wrong - that is, going wrong as far as I've understood the process. Many thanks. Nic

er, a luvvie is as a luvvie does. (writer, blogger, smoozer, snogger).

What did the slug say to the snail? "Big Issue, sir?"

Are the wireless NICs configured by Windows or by a third party application such as something from Intel? If the former, I'm afraid I can't help further, if the latter then you may succeed by disabling that software (which may only run after logging into Windows, hence no wireless pre-login) and using Windows to configure the card.

Get to a command line and type fdisk -l Note the number of cylinders reported and see if there is a partition that ends on this cylinder +1. There probably is. Using fdisk again, delete the partition(s), then create a new partition, ensuring that end of the partition = the cylinder count report by fdisk -l. This method works where gparted doesn't seem to. I do not know why gparted fails, or why this works, or why there should be cylinders outside the number of cylinders the disk has. It's all crazy.

Q. Who led the pedants' revolt? A. Which Tyler. - Private Eye

What is building a network Vs "learn Vanilla AD/Windows networking"? Cripes! I've been at it a few years and I learn something new frighteningly often. Knowing AD/Windows networking like you know your times-tables isn't going tosolve your problems or find your solutions. Hmm. Yer man, we'll be in and out. Fsck 'em. Group Policy isn't off the shelf - here is no M&S suit. It works for one place, it doesn't for another. Hmm. N

It came to my attention recently and after pratting about with Exchange ActivSync on iPhones and a Blackberry chappie expecting the SMT's Blackberries to just work with our exchange server that something was amiss (the clue there was that "if the email client isn't on then then the blackberry can get the message"). Ah hah. POP! Ah hah! IMAP. Anyway, turns out the IMAP VS never starts properly after the server reboots unless you tell, by means of editing the registry, the server to wait a bit longer to discover the domain topology. I suppose that while we think of the IMAP VS as serving the internet, it also needs to serve the local domain and if that doesn't exist you can't really blame it for giving up. XADM: Exchange 2000 Services Do Not Start and a "0x80040a01" Error Message Is Logged - had the answer for me.

There are a few on eBay: The Curse of Monkey Island, Video Games, Books, Comics Magazines, PC items at low prices on eBay.co.uk

Are these groups that give administrator rights to users on local machines? Who are the members of the groups?