|
Aug 03
|
Browsers, Fun and Cool Stuff, Microsoft, Performance, Remote Protocols, Server 2008, TV and Video, Thin Clients, VDI, Virtualization, Windows 7, vWorkspace
|
So last week I managed to get RemoteFX up and running from a Windows 7 VDI from a Hyper-V Host – initially I was a little perturbed as it didn’t look that good, and appeared to have a certain amount of stutter to it, I then realised that I had at some point unplugged the ethernet cable from my Docking Station and as a result I was actually connecting via WiFi – once I replaced the ethernet cable all was fine and the experience was very good indeed.
It’s possibly worth noting here two immutable facts regarding Desktop Virtualization (in my opinion):
- You need to be able to provide a User Experience that is as good as, or better, than a PC today otherwise your project will definitely struggle and may even be doomed to failure before getting to the Pilot stage
- The User Experience cannot be simply defined or quantified – it is extremely subjective, and as such it is very much a “movable target” and subject to the whims of those being asked at any given time of day, etc… (my advice is to aim high
)
So while it was running on the WiFi I tried checking for any latency? None – all 1ms or less – and yet there was some noticeable stutter in the replay of a Flash vide from YouTube.
This brings up another point regarding testing the User Experience – find yourself something that you would consider to be a good representation of what the users would normally use and then continue to use that as a reference model against which all solutions can effectively be measured? – I am currently using a High Definition video clip from YouTube from BBC2 that is an underwater shot of Surfing. This can be found here:
The reasons for using this clip as my reference piece is:
Regardless of who I am showing this to – they will instinctively know what it should look like, even if they have never seen the clip before.
Because of the Slow Motion video it will show up any stutter or frame drop quite dramatically
It is available in a number of resolutions – 240p, 360p, 480p, 720p and 1080p.
It is also quite a good clip and will naturally draw peoples attention
Now after replacing the WiFi with the ethernet cable all seemed to go well at the standard 360p so I thought I’d simply push it higher and all should be OK? Well 480p wasn’t too bad, but anything above that started to suffer, so after doing some checking I noticed that the VDI instance was flat lining the CPU at 100%. So I stopped the VM, added another vCPU and restarted, and then tried again – now it could be run at 720p and only when it was run at 1080p was there some very slight (almost negligible) stutter.
Now this should not be considered as anything like a definitive guide to the performance you might get from RemoteFX – I have had very little time to do any further testing, and next on my list is to get vWorkspace running on this rig so that I can see what difference EOP Xtream makes to these same observations – but in the meantime I’m just sharing my 2 cents worth in the vain hope that it might be useful to someone else?
written by dcaddick
After doing some serious digging it appears that there was well over 400 sessions at MS TechEd 2010 – to be honest I ended up giving up as I figured I’d found way more material than I will be able to get through in quite a long time.
MS are to be commended for being quite open about sharing the content? It would also seem that most of the sessions have been captured on Video as well and are available in HD and MP4.
Here’s my pick of what might be topical and somewhat related to Client and/or Desktop Virtualization?
written by dcaddick
I came across this very interesting post today as something that both validates the “Client Virtualization” approach (I think VDI is a bit too narrow as a definition?) and yet at the same time tells a cautionary tale about how it’s not as easy as it’s sometimes made out to be? and it is way harder than simply Virtualizing Servers
However I think the point can be made that if it is approached in a structured manner, and you do take the time to run through the various steps of PoC, Pilot and then phased deployment while validating each step to check for issues then you should be on-track.
My experience so far is that it’s not really fair to blame “Client Virtualization” or VDI if the IT Dept. has brought in all the old baggage with “this is always the way we have done it”?
Justifying VDI – Part One
April 26, 2010 — David Freund
As Chris Murphy explained in his video blog post, EMC IT began last year to implement a virtual desktop infrastructure based on VMware View. The VDI concept is pretty straightforward, and sounds compelling: reduce desktop management complexity, more cost-effectively update aging desktops (and their operating systems), and give users greater platform choice—and “anywhere, anytime” universal access.
Can VDI really deliver its user experience promise? How much it would really benefit our company in cost savings and in increased flexibility? EMC IT came up with answers to those questions—and got a “green light” for deploying a production VDI environment during the second half of this year.
……
The latency “pain threshold” ended up being around 100 milliseconds. For local users, where network latencies are typically much shorter, virtual desktop performance was similar to a physical PC. For remote users with latencies exceeding 100ms, remote desktop performance was consistently slower than a local PC.
……
In my next post, we’ll finally look at TCO/ROI numbers that helped gain approval for next phase of EMC IT’s VDI project: a production rollout for 5,000 of EMC’s 40,000 desktop users.
Justifying VDI – Part One « EMC IT’s Journey to the Private Cloud
written by dcaddick
Just a brief update as to some of the changes that I have discovered in WES 2011 CTP2 (as opposed to the original CTP) – this was simply built on a default VM Template based on Windows 7.
Also some useful reference links:
Please review the screenshots below (sorry about the quality, I’ll redo them this week)
- There are additional Templates (including Thin Client) that seem to have most of what people would need to get themselves started
- The Summary page then indicates anything that’s not there – in this case the VMware Drivers were missing – I just ignored this and moved on, once completed it appears to have managed to find it and installed it
- Disk Footprint
- This is a huge improvement on the first CTP – Minimal install used to be 650Mb, and just adding Explorer ONLY saw it jump to 2.6Gb
- Estimated OS footprint was listed as 1946Mb for the Thin Client template
- After installation it appeared (at least in the VM as only 1.57Gb)
- To be fair – there does not appear to be too much installed by default though?
- It looks just like Windows 7 – seriously
- So without even telling it what HW I have just check out the listing from Device Manager – only two items were not sorted!!
- No drivers were installed or referenced by me – I just let the wizard do its thing and here it is with the Internet working
- One curious thing I noted was that there is no RUN command, or Search function in the Start Menu, not that this is a bad thing on an intended Thin Client?
- I was able to check that both FBWF and EWF is installed by default
- As things stand I’d say this is a huge leap forward by Microsoft from the disk space point of view as it now looks quite likely that with some judicious pruning then a relatively useful Image can be created to simply act as the dedicated Client Device for Citrix, VMware VDI instances
- If you’d like to get your own copy of the Image Builder Wizard (IBW) then log on to connect.microsoft.com to download
So after thinking on this some more I had the following thoughts?
- This is essentially Windows 7 “super lite” and appears to be pretty much compatible with everything
- It’s so easy to build a new runtime it no longer needs a developer to create bespoke instances?
- Comes with the choice of enabling either Enhanced Write Filter (EWF) or File Based Write Filter (FBWF) to protect the base image
- A “Thin Client” install is only 1.5G in size – well down from the standard Windows 7 with Office reaching more like 20Gb
- Sure – the terms of the EULA specifically prohibit the *install* of Full MS Office Products
- But that doesn’t preclude any Application Streaming or Virtualization efforts?
- At only USD$90 a runtime version, and only 1.5Gb – will this be *THE* VDI base OS of choice?
- It’s small, light, cheap AND it is non-persistent straight out of the box – it’s certainly worthy of some consideration?
 
 




written by dcaddick
|
Dec 23
|
App Streaming, Citrix, Finance and Business, Microsoft, Networks, Performance, Remote Protocols, Thin Clients, VDI, VMware, Virtualization, Windows 7
|
So as things slowdown in the lead up to the break I have had some time to get back and review some twitter posts and other blog articles that I have been meaning to catch up on. I must admit that I tend not to use Twitter that much but do find it quite useful as pointers to additional material for research and recently posted material on the topics that I’m interested in.
So one article that really caught my eye was this from Ruben Spruijt’s post at Brian Madden, because for a number of years now it is the Hard Drive that has not kept pace with advancements in technology for the rest of the PC/Laptop components, and in particular I have noted a number of people getting very enthusiastic about the performance improvements they have actually noticed when using Laptops with SSD’s
Runcore SSD’s – promises to boost computer performance vs. the traditional 1.8" HDD by more than 400% with read/write speeds up to 75/40MB/sec. Experience with 128GB 1.8" ZIF in HP 2710p – Read/write performance for 4K random files has improved over 500% (even under Bitlocker). it just became the fastest computer I ever used… Word and Excel launch in one or two seconds (compared to 30-60 before)…
Just how fast does the storage component of VDI have to be? So it stands to reason that if you are going to Virtualize your Desktops (and by definition centralize?) then you are going to need to give some serious throughput for the Disk I/O or IOPS? So for anyone who is embarking on this then I would seriously recommend giving this article a through read? Understanding how storage design has a big impact on your VDI!
Possibly the most interesting point that Ruben did bring to my attention with this is that in VDI implementation the Disk I/O is predominately Writes and not Reads – I know this sounds contradictory in some respects, but do review this for yourself – in particular is a good comment from Claudio Rodrigues regarding the nature of how the O/S’s deal with this, as well as confirmation from Dan Feller at Citrix who confirms that most of the numbers and math are in sync with his findings. Ruben has also supplied a Sizing Tool to get a good idea of what might be needed?
So it also starts to make sense that you make sure that you focus very sharply on the XP or Windows 7 Template VM’s in the first place to reduce the I/O required as much as possible? Citrix has some great tips in this document - Best Practices – Citrix XenDesktop with Citrix Provisioning Server
So as this brought up some interesting thoughts I also found this article relating to sizing and best practices, VMware View sizing & best practices which followed on from this original article Virtual Infrastructure best practices and in essence this confirms that the storage requirements will need to focused somewhere around an 20/80 split on the Read/Write (20% read and 80% write)
While this table gives a quick representation of what sort of sizing requirements are out there please make sure you research this subject thoroughly, and read the post in full? J
In all fairness I must also confess at this point that my weakest area in IT is storage, and as yet I have not had a functioning Lab running either Citrix’s XenDesktop or Vmware’s View to be able to play around with this and get my hands dirty with either Provisioning Server or Composer. From what I can see (based on Marketing so far J) both of these products have the ability to drastically minimize the storage needed for VDI and as a consequence I am assuming that this may indeed have a flow on effect to mitigating the IOPS issue? (Can anyone comment or set me straight on this?)
I then went on to find some more details around the costing and financial side of VDI implementations and found this article of Doug Brown’s regarding Cost Savings of VDI: Is It Possible? as the diagram below points out, it is complex, and as such it could be that the regular ROT/TCO calculations are not highlighting all the potential benefits and savings?
Changing the ROI/TCO Calculation? So this then brings me to another update in my Twitter was from Tyler at LiquidwareLabs.com with a new addition to the ROI/TCO debate, COP – Coefficient of Productivity in VDI the New Math , in which he points out that you should also factor in any additional productivity gains and use this to dilute the true cost of the CAPEX.
Now I wonder how many VDI proposals are brave enough to start assigning values to what has traditionally been seen as "additional" benefits related to an architectural change? Don’t get me wrong, I’m not against it, but I can see the debate might start to get a bit heated in the boardroom? and in some respects maybe that’s exactly what’s needed – by assigning values and assumptions and then extrapolating them across an enterprise the resultant *potential* savings become too hard for the board to ignore?
Sure there will be debate, and rightly so, but in following this sort of process it should quickly become apparent that there is a technological shift under way where the concept of "My Desktop" still being something that can be pointed to in the Office sitting on a desk somewhere is rapidly becoming redundant?
Now having said all that – it’s interesting to note that Gartner’s Hype Cycle Report for 2009 seems not to have VDI listed? Maybe it’s hiding under something else here?

So will VDI make it to "mainstream"? AMD seems to think so, Taking Desktop Virtualization Mainstream, but also a lot of it will depend on a number of factors.
My main thoughts on this are:
To truly succeed VDI needs to be able to deliver a *High Fidelity* User experience equal to or better than what users have today – if what you are designing is unable to provide this then you should stop and re-evaluate now
If you can build a system that is able to provide this then users will want (no, Demand!) that they have it ASAP – you will know that you have succeeded when demand outstrips supply
To provide this *High Fidelity* User experience I’d suggest focusing on two key areas that may/or may not apply depending on your particular focus and what is considered in or out of scope for your project?
-
Graphics
- Bottom line – Graphics performance in this design CANNOT be measured, it has no metrics, or Best Practices. One persons "that’s fine" is another persons "there is absolutely no way I’ll put up with that", etc. This will always be a completely subjective assessment based on whoever is rendering the judgement.
- You may think that you don’t need to focus too much on Graphics because "there isn’t much need or requirement for Video from the business" but I can almost bet that you would be wrong – if you are operating on this assumption be sure that you double-check with Stakeholders and get their agreement in writing?
- So much content on the Internet is done in Flash today, it’s not just watching a CEO or Analyst briefing via YouTube, a lot of Web Based Training modules use the same or similar technologies, so even if you currently block YouTube and Facebook today it’s still quite likely that you need to factor this in to your design
- Is RDP good enough? Check this assumption by giving targeted business users a Thin Client and removing their desktop to the lab and forcing them to access via the Thin Client – this is a simple but effective test that validates whether they truly need/demand High Fidelity, or will OK Fidelity do?
- Do you need Citrix HDX? PCoIP? RGS? While I’m making the point about Remote Protocols – don’t forget to gather details of connecting accessories? Do you need to support serial or parallel?
-
HDD or IOPS
- Make sure the VM performs as well as possible while measuring the I/O on the VM itself? Check the disk queue, and ensure that it’s not the disk performance that’s holding this back – and make sure you have enough throughput to allow for Login’s etc.
So where does that leave us? In the Graphics space there is already a number of solutions for VDI that have been out for some time (Citrix’s HDX) or have recently been released (Teradici’s software version of PCoIP). In addition to that there are other approaches if you need to support High Fidelity Users at the top end with HDX-3D taking advantage of Nvidias GPU’s that almost bring TeraFLOP performance to the Desktop.
A good introduction to CUDA – Just how powerful can GPU’s be? Back in mid-2008 the GT200 was able to deliver 1 TeraFLOP performance, the G80 supports 768 Threads per Core – on 128 Cores… Want a Personal Supercomputer? What would you use it for?
So I suspect that we are not far away from seeing vGPU’s being available to VM’s that will be able to deliver the performance on demand – the main thing is that you make sure you are either using a Remote Protocol stack that can provide this functionality – OR make sure you are using a Broker that supports a shift to one?
At the HDD level I’d suspect that as SSD prices come down and SSD longevity increases, along with improved methods of utilising this in some kind of shared caching mechanism in a VDI deployment we may well see some serious advances that enable VDI to overcome this IOPS roadblock?
With the monotonous regularity of Moore’s Law driving CPU performance up it should be possible to provide way more CPU power to users than they really need to enable this – but again – it’s quite possible that the Disk I/O that has the potential to spoil this party?
Please feel free to correct any of my ramblings?
written by dcaddick
The best piece I have read from the IT Industry in the last two weeks or so is:
Desktop virtualization is one of the hottest topics of interest and a major initiative of many companies. Touted benefits include lower operating costs, simpler management and desktop mobility. Below we’ll explore what the barriers to wide-scale adoption of desktop virtualization solutions are and some approaches to deal with them. It’s not a fit for everyone in a company but it can be for many.
Challenge #1: Assuming desktop virtualization makes sense because thin clients are cheap - Many people assume that virtualizing desktops is going to be magnitudes cheaper because thin clients can be found for approximately $300-400 whereas a PC can cost $500-$1200.
Tip: Client costs are only part of the picture. Desktop virtualization can reduce capital expenditures but do not expect that to be the case in the first year. Building the infrastructure is expensive (storage, servers, licenses, etc.) and may be the same in the first year. Think about using existing PCs as clients instead of replacing them with thin clients. Thin clients are cheaper than PCs but the reduction in hardware costs may not be seen for a couple of years due to the infrastructure needing to be built. More importantly, operational expenses will be seen immediately and that is where the true cost savings can be found.
……… more at source
I have also collated below some of the details I have discovered around the latest news on PCoIP and HDX-3D
From Brian Madden:
For me the most crucial part of this post is explaining this:
How HDX 3D works
On the remote host side, Citrix is releasing a custom VDA for the environments where you want to use HDX 3D. (The VDA, or “Virtual Desktop Agent,” is the software agent you install on your remote workstation OS that lets it participate in a XenDesktop farm and gives the ICA hosting capability to a desktop OS.) Having a separate VDA shouldn’t be a problem for anyone since this is a physical workstation host solution anyway, so it’s not like you’re sharing the same disk image with remote desktop VMs.
On the client side, HDX 3D is just another plug-in for the Citrix Receiver. (That’s newspeak for “it’s just another virtual channel for the regular ICA client.”) HDX 3D lets you configure the image quality, so you can balance the bandwidth-to-user experience. (PC-over-IP lets you do this too.)
From a technical standpoint, the HDX 3D engine replaces the existing ICA progressive display capability. It lets the OpenGL or DirectX stuff render on the host, and then it scrapes them and makes what’s essentially like an M-JPEG movie which is streamed down and played on the client. In many ways this is similar to the way HP RGS and Teradici PC-over-IP.
………. more at source
What this tells me is that this is right in the zone for HP’s Blade Workstation’s as they have Nvidia based GPU, and that the BladePC’s would not be in at all as they are AMD/ATI based hardware. It’s also interesting to note some more details coming out via this Citrix Community Blog HDX 3D – What Happened to Projects Pictor, Apollo and Prism? and the subsequent comments from Sridhar Mullapudi, Sr. Product Manager:
Though the first release is available for only XD customers, future releases will enable XA customers to get HDX 3D using VM Hosted Apps technology. And with GPU virtualization and related technologies in the future, we will enable support of HDX 3D on virtual machines as well.
And for VMware Brian Madden had this commentary…
The irony of this is that I really, really want VMware to be successful with desktops. Competition from VMware has caused Citrix to put more innovation into their desktop delivery products in 18 months than they have in the past ten years combined. If VMware rolls over on the desktop, I hope that the Symantec or Quest can step up to apply pressure to Citrix or else we’re going to have another decade of innovation ice age.
But back to the main topic: VMware’s lack of desktop vision.
At last year’s VMworld, we got all these great indications of what VMware was capable of in the desktop space. (Here’s my article from then where I could hardly contain my excitement about six desktop announcements.) And how did VMware follow up at this year’s VMworld?
So those were two great things. (Tactical, but still great.) Unfortunately that’s kind of where the good news from VMworld stopped:
- VMware demoed their client hypervisor known as CVP. (yay!) But we learned that it won’t be available until 2H 2010! Last year they said their client hypervisor was going to ship by the end of 2009, and now it’s another 8+ months away!?!
- The View futures session was just about View 4. VMware still hasn’t announced a release date, although the rumor is it’s still coming at some point this year. View 4 will have PC-over-IP, but little else new. (Oh, it will have vSphere 4 support.)
………… more at source
from Citrix Community blog:
- Desktop Virtualization is not Server Virtualization (This title pretty much tells it like it is)
- Setting the Record Straight on XenDesktop (there’s not that much difference between XenDesktop and View apparently?
)
- Interesting comment towards the bottom – Lastly, while I differ with most of what one VMware Community member, Rkelly, posted re View vs. XenDesktop, I have to say I agree with his final point for the IT team in any VMware shop: "Download the trial versions of both products and see for yourself" . You just can’t beat a “Try before you buy”
From Alessandro and Virtualization.info
 
The company already has a Xen-based client hypervisor and a fairly complex web-based console which uses virtual machines, snapshots and clones to publish the right system environment to the right user with the right customization. Now Virtual Computer also simplified the management of the application layer thanks to a technology partnership with XenoCode, the application virtualization company that already has an OEM deal with Novell.
Compared to the Novell agreement, Virtual Computer is not OEM’ing the XenoCode Virtual Application Studio. It is just supporting the applications virtualized with the XenoCode technology out-of-the-box inside its NxTop virtual machines.
It is not a revolution but this way Virtual Computer is silently building an end-to-end VDI stack that one day could rival with the upcoming ones from Citrix and VMware.
And lastly…. I haven’t see this before? The AppFactory, based in UK from the looks of it and promising to Virtualize your Apps from 149 pounds an App? I wonder how well these guys will do? Very slick and professional web site, so it will be interesting to hear how well they do?
written by dcaddick
Hi All,
I have created a number of HyperV Servers that all have at least 1 instance of a Windows 7 VM running – and yet it seems that the Admin Tool from MS is *very* restricted in that there is no way to *pick* the VM’s up? They have to be auto-recognised somehow?
With View, XenDesktop and SAM *we* have to go and install the agent Software on the Hosts – there does not seem to be any info around this?
Does anyone have any additional info as to how to get this working?

written by dcaddick
So it’s hardly a surprise that Citrix have decided to “Announce” the long awaited HDX-3D “high quality user experience” protocol enhancement in the early hours prior to the start of the VMworld conference? Pardon me for being something of a sceptic, but it seems that this might have more to do with the fact that Teradici are expected to release the Software only version of their PCoIP protocol stack in Public Beta at this event?
I’ve had a look around the MyCitrix.com site and from what I can see there is no new components as the latest update was the addition of the Feature Release 1 update of the XenDesktop Agent component back on the 5/1/09? I’d be more than happy to be proved incorrect, but I’d imagine that if Citrix had actually posted this new component up on the web site as an available download then they’d be making sure it was “in your face”?
I’m pretty well acquainted with RGS and it’s capabilities, so I’m quite keen to get my hands on both of these new technologies and give them a going over to find their strengths and weakness’s. One of the biggest issues/problems is that the visual quality that is delivered is subject to “peoples perceptions” and as such can be quite difficult to comparisons? One persons “great”, can be another persons “rubbish”?
I’ll be at Microsoft’s TechEd 09 on the Gold Coast here in Australia next week (on the HP Stand) and I’m hoping to be able to do live demonstrations and comparisons of RDP6, RDP7 and RGS so that Customers can see for themselves why implementing the correct Remote Protocol stack can be crucial depending on their particular circumstances.
Citrix Enhances Market Leading HDX Technology for High-Definition Virtual Desktops
Mon Aug 31, 2009 3:01am EDT
Breakthrough New HDX 3D Technology Enables Citrix XenDesktop to Deliver High-End
Professional Graphics in Real-Time over Any Network
SANTA CLARA, Calif.--(Business Wire)--
Today Citrix Systems, Inc. (NASDAQ: CTXS), announced a new breakthrough addition
to its market leading HDX Technology, ensuring a high-definition virtual desktop
experience even for the most demanding high-end professional graphics
environments. The new HDX 3D technology, available as a feature of Citrix
XenDesktop, delivers a rich, high-definition desktop experience applications to
users in any location, over any network. Combined with the full portfolio of HDX
technologies in XenDesktop, the new HDX 3D capability allows organizations to
leverage talent globally, while still housing data centrally, assisting in
real-time collaboration among disperse design teams while still ensuring the
security of critical intellectual property. HDX 3D is part of an extensive range
of HDX technologies from Citrix that go well beyond a single protocol to address
potential problems in all parts of the IT infrastructure, from the datacenter,
to the network, to the device. Combined with the company`s groundbreaking HDX
Adaptive Orchestration technology, XenDesktop can also dynamically adapt to
changes in the environment by applying the best technologies for each unique
user scenario (see http://hdx.citrix.com for more detail).
Citrix Enhances Market Leading HDX Technology for High-Definition Virtual Desktops | Reuters
written by dcaddick
|
Aug 18
|
Hardware, Microsoft, Networks, Performance, Remote Protocols, Thin Clients, Troubleshooting, Vista, WiFi, Windows 7, XPe
|
Some while back one of my US based colleagues passed on some advice about checking out some details on how to get the best out of Wireshark
For anyone interested in getting their feet wet using Wireshark the network protocol analyzer. This knowledge can be useful to have when dealing with network anomalies.
www.chappellseminars.com/s-wireshark101.html
Download the latest 1.2.1
As you may or may not know this was originally called Ethereal, and then morphed in to Wireshark, and has recently had quite a number of improvements and has moved from ver. 0.9 to now 1.2 plus in the last few months. There has been quite a number of additions including the ability to graph throughput etc from within the tool, as well as it now supporting GeoIP DB’s so that you can carry out extensive mapping of where the packets are going to or coming from.
http://wiki.wireshark.org/HowToUseGeoIP
Running Windows 7?
If you are running Windows 7 – then do be aware that the WinPcap driver (the component that does the sniffing) will fail to install by default – but if you modify the executable to run in Vista SP1 compatability mode then all should be fine – as detailed below:
I’ve just downloaded WinPcap 4.1 beta5 from here: WinPcap, the Packet Capture and Network Monitoring Library for Windows Set the compatibility mode to Windows Vista (right click on the installer executable then select Properties; on the Compatibility tab, check "Run this program in compatibility mode for", select Windows Vista SP1 from the dropdown list, then finally click OK =)) and it will install as it should. For me it worked flawlessly so far.
Further reading
I then followed this up a bit further and noted that after a recent Sharkfest event there were a number of presentations made by a chap called Ray Tompkins (CEO of Gearbit) and these are available at:
At Sharkfest 2009 gearbit presented 3 sessions:: Finding the Latency: How Protocols Work: Wireshark Charts & IO Graphs: OSTU – Wireshark IO Graph for Response Time Analysis: Understanding the Need for Protocol Analysis: HYPERLINK OSTU – Wireshark Case Study: Benchmark Test OSTU – Wireshark TCP Stream Graphs OSTU – Wireshark Capture Filters OSTU – Wireshark Display Filters OSTU – Identifying Zero Window with Wireshark
If you do find that you have to dig in on a Customers Site to start doing some serious troubleshooting around Networks then I would seriously recommend the first two presentations in PDF format as they do appear to explain things in a very simple and matter of fact way.
Wireless Issues:
Now this should in no way be any sort of substitute for a proper Wireless Survey, but when you find that you are up against some issues then try using inSSIDer as a very good starting point? And it works on Windows 7 straight out of the box

written by dcaddick
So I noticed some good info coming out of the MSDN Terminal Server blog, like:Introducing Remote Desktop Connection Manager and I was reasonably curious if the RDS Brokering would allow you to attach or add Physical devices like BladePC’s or BladeWS’s to the Virtual Pooling of resources available for users to RDP in to. So I figured the best way was to dive in and give it a shot?
So it seems like there are certainly no issues with installing Win 2008 R2 in a VM based on the VMware Workstation 6.5, remembering that there is no longer a 32 bit version. So here is some of what I found with the install:
Page 17 shows what the Web Access page looks like (needs to be HTTPS – self signed cert is fine)
At this point I was able to successfully enter the details of my Windows 7 Laptop in the “Connect To” field and then the session on the WIN2008 Server was able to bring up an RDP7 (6.1) session
To double-check I’d need to access this web site remotely from another machine and check that works? But to be honest I was mainly after just figuring out if I could attach physical units so I’ll leave that for now.
Details of what can be configured under the RDS
![clip_image002[6] clip_image002[6]](http://www.techagility.info/wp-content/uploads/2009/07/clip_image0026_thumb.jpg) ![clip_image002[8] clip_image002[8]](http://www.techagility.info/wp-content/uploads/2009/07/clip_image0028_thumb.jpg)
Page 25 shows: Trying to specify devices that can be connected to – and it quickly becomes apparent that you can only add Virtual Devices to the mix – I now need to add Hyper-V to this Server (if it’ll let me?) and then I should be able to add VM’s to the pool for assignment
Bottom line – to add additional devices apart from virtual VM’s this would quite likely need a hack? to effect this and so here is where my investigation ends for now.
So this is all of the post for now and I’ll try and place a link here for the full document (1.9Mb)
written by dcaddick
|