One of our batch of Lenovo T500 laptops refuses to boot from our Windows Deployment PXE server.
So not easy to get our default company image into it. Hard to explain to Lenovo support what is wrong cause its so very specific. All other network functions are just fine. My colleague ran a trace on the server side, and the Laptop doesn’t even seem to contact it.
If I had to guess I would say its network driver issue and this laptop has a very specific revision of network board .. or something.
It seems I am not the only one running into PXE boot issues with a Lenovo.
Don’t really have that much time to dig deeply into it. I would like to see what the conversation is between our WDS server, the DHCP server and the laptop. Something wierd going on there.
Tags: bootp, DHCP, Lenovo, Lenovo t500, PXE, T500, WDS, Windows Deployment Server
A bit of relaxed late-night admin from the comfort of the big cushy chair. 
Here is a brand new Lenovo Thinkpad X200 that has been running on a single charge for over 6 hours now, non stop (ultra low power mode). I am connected into work via our Citrix access gateway, logged into an admin desktop on Citrx, and am in fact rolling out a Citrix server remotely.
On the right of the screen is the big RES Wisdom job that runs the installation script. As you can see the entire process is hands-off. On the left is the console of the server, connected via the ILO. I dont need to do anything on the desktop, I just monitor it there and it gives me something to watch.
Tonight and this weekend, we are upgrading our Livelink document management system.
Tomorrow is also “Sinterklaas”, and it is traditional to send eachother lame poems as part of it.
So here is mine to all the users, to get them to log out on time:
Sint en Piet zaten te bedenken
Dat pakjesavond er is voor geschenken
Weet je wat het NOB in het schoentje vindt?
Een NECTS Release 1.2.1 met de groeten van Sint
Zo’n update door te voeren kost heel veel duiten
Daarom vraagt Piet aan iedereen om zo dadelijk af te sluiten
Zo hoeven de IT-ers niet lang te wachten
Om jullie Livelink pijn te helpen verzachten
Dus gaarne zo spoedig mogelijk af te loggen
Zodat het systeem dadelijk niet zal ontploffen!
Een voorspoedige reis naar huis, en wat betreft pakjesavond: geniet!
Heel veel groeten van de Sint en van Piet.
Sent over Citrix to all logged-in users:
As many before us, we ran into the following error in Virtual Center, when we tried to P-to-V a server:
“multiple connections to a server or shared resource by the same user”
This is not an uncommon error, and you might recognise it from other scenarios that involve remotely connecting to a Windows host.
I found quite a few posts that mentioned this problem, even a mention in the release notes of VMWare Converter itself, and an VMware knowledge base article, and they go something like this:
An Inter-Process Communication (IPC) named-pipe network connection is already open from the local Windows Redirector to the remote host with different credentials than you are specifying in Converter. The Windows Redirector does not allow IPC connections with multiple different credentials from the same user session. This restriction also applies to mapped network drives as they are also a type of named-pipe connection.To ensure the Converter agent connection succeeds, perform the following actions on the computer running Converter:
Note: This disconnects any mapped drives to the remote host.
So we tried all the above, but to no avail. Try as we may, from both our admin workstations, aswell as on the Virtual Center server itself, we could not get it to run.
In the end, my collegue tried to run the task using the IP adress of the server, itstead of its hostname!
That did the trick! But don’t ask me why! I suspect it has something to with the named-pipe actually being named differently when you do this.
Tags: error, multiple connections, virtual center, vmware, vmware converter
:p
Recent Comments