XWin window manager with virtual desktops

So I'm resuming my search for an X11 window manager that provides virtual desktops. I also would like just a little bit of keyboard customization, i.e., assign an F key to raise a window. Keystrokes to move between virtual desktops would be nice.
Any suggestions?
Blackbox, from Darwinports, seems very nice in a lot of ways, but to get a visual interface to its virtual desktops you have to add bbpager. Darwinports does not have bbpager, and Blackbox needs a newer version of bbpager than the one on fink. Building bbpager from source myself appears to work, but an attempt to run it gives:
dyld: lazy symbol binding failed: lazy pointer not found
dyld: lazy pointer not found
Trace/BPT trap
At which point I'm in over my head.
A while back, AfterStep 1.8 did everything I wanted, but nobody maintains it for OS X anymore, as far as I can tell. AfterStep 2 is maintained, but the default style has changed not to my liking, and then and now customizing it is complex.

Hi Don,
   It's good to hear from you, as always! I believe that the lazy symbol binding failure is the result of the use of the wrong version gcc. I think that it happens when you use gcc-3.3 when gcc-4.0.1 is required, although I could have that backwards; it hasn't happened to me yet. I don't know why some apps would require a new version of gcc when most don't.
   It appears that Jonathan's suggestions are for virtual desktops for Aqua and not X11. Of course given your taste for virtual desktops, that is likely to be something of interest to you.
   As for virtual desktops for X11, they abound. My preference for a window manager that implements virtual desktops is Enlightenment. I like it for other reasons but it has a nice virtual desktop arrangement that "plays well" with Rootless mode. The desktops are arranged in a square. By default, the top two desktops have no background image, while the bottom two do. This allows one to use Enlightenment's elaborate contextual menu, which I like. There are numerous subtle features that make using desktops convenient and I think you'd like it.
Gary
~~~~
   A "practical joker" deserves applause for his wit according
   to its quality. Bastinado is about right. For exceptional
   wit one might grant keelhauling. But staking him out on
   an anthill should be reserved for the very wittiest.
         -- Lazarus Long

Similar Messages

  • Requesting API calls for Windows 10's virtual desktops

    Please add API calls for working with Windows 10's virtual desktops, for example, a way to determine which virtual desktop a particular window is on and which virtual desktop is active.
    The problem can be seen using the Snipping Tool. Open the tool and select a
    New / Window Snip. As you move the mouse around, the snipping tool
    highlights areas where there is no window, but there is a window in another virtual desktop.
    First desktop, Snipping Tool highlights and empty area ...
    Second desktop...
    It's because Snipping Tool has no way to know which virtual desktop a particular window is on.
    Thanks!

    Thanks, been there, did that, but there's no way to know if Microsoft listened or provided a solution :-(
    Hi GoVideo,
    Currently, Windows 10 is still in the Technical Preview stage, Microsoft will collect all feedbacks and evaluate them guardedly.
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • RDS 2012-PUBLISING REMOTEAPPS WITH VIRTUAL DESKTOP SESSION

    Hello,  I deployed a RDS 2012 VIRTUAL DESKTOP SESSION FARM.
    Is it possible publish a REMOTEAPPS with Virtual Desktop Session?, I only find information with Remote Desktop Session
    Thanks
    Regards

    Hi,
    Seems this is not the possible scenario for deployment, we need to have Session based deployment as both virtual desktop session and session based deployment differs from other.
    Thanks.
    Dharmesh Solanki
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • VoiP with Virtual Desktops

    My company is switching over to VoiP with HUD and we are also looking into using the Virtual Desktops with existing PCs. Will the phone system work with VDI?

    Hi
    VDI is base in RDP or X11 protocol.
    With Windows 2003R2, the RDP sound is on way only. The RDP is not bidirectional yet.
    Microsoft plan to put is in Windows 2008R2 Server but is only roadmap.
    Best Regard's
    Marcelo Moreira Martins
    [email protected]
    Technical Consultant - Tarantella Systems Engineer
    SE- Systems Engineer - M3 System Integrator.
    Sun Microsystems do Brasil - Authorized Reseller
    VMware VIP Partner
    +55-51-3333-2644 - Porto Alegre Office
    +55 11-4063-6584 - SP
    +55-51-8167-9382 - Mobile Phone
    Visit the EduSoft web site: http://www.sun.com/edu/edusoft/

  • New window manager (with prototype!) [wmii-like] --- looking for help

    I have a prototype for a new window manager in the style of wmii. It is called
    cakewm. I currently have a prototype version implemented in pygame, and would
    like help moving this to use X---making it a real window manager.
    Disclaimer: I have a very limited knowledge of X11 and window manager
    development. The most I've done is add a couple new features to wmfs.
    To get the code
    > git clone git://github.com/saikobee/cakewm.git
    Then run main.py. cakewm depends on pygame.
    Upon running, press Alt-Enter to fullscreen cakewm and intercept keybinds, or
    Alt-Space to just intercept keybinds.  Press Alt-Esc to quit. The window
    manager related keybinds are listed in the file binds.conf.
    Config note: <WSCA-x> means Windows-Shift-Control-Alt-x
    Implementation note: pypixel.py is a large and mostly useless dependency. I
    forked a library I made previously rather than coding straight in pygame.
    cakewm's goals are to be similar to wmii, but with more functionality, easier
    configurability, and saner defaults.
    - cakewm is fully functional using the keyboard. Mouse support can come later.
    - cakewm provides 9 workspaces per monitor.
    - cakewm manages each workspace as a group of columns. Each column is like a
      wmii default split, except each window can have other windows "stacked" on
      top of or behind it.
    - cakewm manages column sizes (and window sizes within columns) using a
      master/slave paradigm, with the ability to adjust the size ratios.
    - cakewm's configuration file is simple key=val pairs, with the ability to
      include other files like in C.
    - cakewm has a slightly larger emphasis on window decorations (adjustable
      size---even in tiled mode) and themes (nothing bloated, like pixmaps or
      gradients---it's all still simple colors).
    - cakewm will have proper support for international text (Japanese text in
      window titles or the wmii status bar generally render as boxes) through the
      use of a more advanced text library such as Pango.
    Please let me know if you have comments, questions, or concerns. If you are
    interested in helping, get in touch with me. If you know somewhere better to
    look for volunteers, please let me know.

    m4co wrote:
    Wow is this forum active. Makes me feel welcome here
    The thing about wireless, I actually like command line, but there are a few things that are worth having a applet or something.
    And wireless is one of those. I guess I can take a look on wicd.
    It's a good idea to have compiz as the WM actually. Would it be lightweight to have it like that?
    Is there anybody here that uses compiz as a WM?
    For the xfce4-panel, is it possible to get transparency on it? That's probably the only thing holding me back with xfce4-panel.
    If "able to run compiz" wasn't a requisite, what other WM would you suggest for my "profile" ?
    I would like to hear other users opinions who like to customize everything on a WM.
    I recommend running Compiz by itself. There is a good wiki page on it in the Arch wiki. Some apps you'll want to go with it are:
    LXAppearance --change GTK/icon theme
    Feh or Nitrogen --Set Wallpaper
    Xfce4-panel --The lightest one that works with Compiz properly
    Or, if you don't want a panel: stalonetray
    Compiz-deskmenu --For a customizable right-click main menu
    Gmrun --Run dialog (Alt+F2 in most DEs)
    And this helped me a lot.
    Thank you all for the replies. I appreciate.
    Xfce4-panel can have transparency.  The only problem is that everything become transparent: text, icons, everything.
    I use Compiz as a standalone WM and it is much lighter than DE+Compiz. My Compiz setup uses about 30MB(out of 1GB) more RAM than my Openbox setup (which are both the same except for the WM).

  • Is there a tiling window manager with anti-aliased fonts?

    Hi,
    Is there a tiling window manger with anti-aliased fonts?
    Thanks.
    Last edited by 9mqks5hn (2009-07-14 18:50:45)

    pauldonnelly wrote:
    cinan wrote:your font configuration has nothing to do with window manager. Hope this helps you http://wiki.archlinux.org/index.php/Xor … figuration
    Any text the window manager displays is rather affected.
    None come to mind here, but that doesn't mean much.
    You can use any panel/pager with XMonad if you use the ewmh hooks (these panels usually support anti-aliased fonts). There is a dzen2-xft version floating around the net somewhere if I'm not mistaken...

  • Wingo: floating and tiling window manager with per-monitor workspaces

    More screenshots.
    Wingo has two features which, when combined, set it apart from other window managers (maybe):
    1) Support for both floating and tiling placement policies. Wingo can be used as a regular floating (stacking) window manager, complete with decorations, maximization, sticky windows, and most other things you might find in a window manager. Wingo can also be switched into a tiling mode where window decorations disappear, and windows are automatically managed via tiling.
    2) Workspaces per monitor. In a multi-head setup, each monitor can display its own workspace---independent of the other monitors. This makes changing your view of windows in multi-head setups much easier than in most other window managers, which will only allow you to see one workspace stretched across all of your monitors. Also, since placement policies like floating and tiling affect workspaces, this makes it possible for one monitor to be tiling while another is floating!
    Inspiration
    Wingo is heavily inspired by Openbox and Xmonad (and of course, pytyle). Basically, Openbox's floating semantics (although most window managers are the same in this regard) and Xmonad's automatic tiling style plus its workspace model (workspaces per monitor). I've also adopted Xmonad's "greedy" workspace switching and embedded the concepts from the "DynamicWorkspaces" contrib library into the Gribble command system.
    Configuration
    Wingo is extremely configurable. This includes binding any of a vast number of commands to key or mouse presses, theming your window decorations and setting up hooks that will fire depending upon a set of match conditions.
    All configuration is done using an INI like file format with support for simple variable substitution (which makes theming a bit simpler). No XML. No recompiling. No scripting.
    Configuring key/mouse bindings and hooks uses a central command system called Gribble. For example, one can add a workspace named "cromulent" with this command while Wingo is running:
    AddWorkspace "cromulent"
    But that's not very flexible, right? It'd be nice if you could specify the name of workspace on the fly... For this, simply use the "Input" command as an argument to AddWorkspace, which shows a graphical prompt and allows you to type in a name:
    AddWorkspace (Input "Enter your workspace name:")
    The text entered into the input box will be passed to the AddWorkspace command.
    Please see the HOWTO-COMMANDS file for more info. We've barely scratched the surface.
    Scripting Wingo
    So I lied earlier. You can kind of script Wingo by using its IPC mechanism. While Wingo is running, you can send any command you like:
    wingo-cmd 'AddWorkspace "embiggen"'
    Or perhaps you can't remember how to use the AddWorkspace command:
    wingo-cmd --usage AddWorkspace
    Which will print the parameters, their types and a description of the command.
    Want to pipe some information to another program? No problem, since commands can return stuff!
    wingo-cmd GetWorkspace
    And you can even make commands repeat themselves every X milliseconds, which is ideal for use with something like dzen to show the name of the currently active window:
    wingo-cmd --poll 500 'GetClientName (GetActive)' | dzen2
    Finally, you can see a list of all commands, their parameters and their usage: (even if Wingo isn't running)
    wingo-cmd --list-usage
    (Wingo actually can provide enough information (or will soon) for ambitious hackers to script their own layouts in whatever programming language they like without ever having to deal with X at all. Assuming it has support for connecting to unix domain sockets. Or you could just use a shell with 'wingo-cmd' if you're into that kind of tomfoolery.)
    Dynamic Workspaces
    Having some set number of workspaces labeled 1, 2, 3, 4, ... is a thing of the past. While Wingo won't stop you from using such a simplistic model, it will egg you on to try something else: dynamic workspaces.
    Dynamic workspaces takes advantage of two things: workspace names and adding/removing workspaces as you need them.
    This is something that I find useful since I'm typically working on multiple projects, and my needs change as I work on them. For example, when working on Wingo, I might add the "wingo" workspace, along with the "xephyr" workspace and the "gribble" workspace. When I'm done, I can remove those and add other workspaces for my next project. Or I can leave those workspaces intact for when I come back to them later.
    With Wingo, such a workflow is natural because you're no longer confined to "removing only the last workspace" or some other such nonsense. Plus, adding a workspace requires that you name it---so workspaces always carry some semantic meaning.
    (N.B. I don't mean to imply that this model is new, just uncommon; particularly among floating window managers. I've personally taken the model from xmonad-contrib's DynamicWorkspaces module.)
    Tiling layouts
    Right now, only simple tiling layouts are available. (Vertical and Horizontal.) Mostly because those are the layouts that I primarily use. I'll be adding more as they are demanded.
    Dependencies
    Wingo is written in pure Go (including all of its dependencies). As such, Go (and git) is the only package necessary to build and install Wingo. Once Wingo is installed, Go can be removed. (No Xlib/xcb, no cairo, no gui toolkits.)
    Installation
    Wingo is in the AUR. Alternatively, if you have a Go environment set up, you can download, build and install Wingo and all of its necessary dependencies with:
    go get github.com/BurntSushi/wingo
    go get github.com/BurntSushi/wingo/wingo-cmd
    (Yes, Go's build system is really that awesome.)
    There's a lot more at Wingo's github.
    Please note that Wingo should be considered in a very alpha state. I've been using it for a little bit myself, but beyond that, Wingo is untested.
    Last edited by BurntSushi (2012-10-22 06:02:16)

    netfun81 wrote:wow, nice wm.  Install was a breeze, love having floating layout on one screen and tiling on another.   In the past, for certain apps that wouldn't play well with a tiling wm, I would have to kill X, change my .xinitrc to start openbox and startx again.   This seems like the perfect solution.
    Thanks :-)
    netfun81 wrote:Does "go get github.com/BurntSushi/wingo"  always pull the latest from git?   Can i just delete the wingo executable from go/bin and run command to upgrade to latest or do I need to delete config files each time to remain compatible?
    Yes, `go get ...` always pulls from the latest git. I make sure that Wingo builds before pushing to `master`. I'll use a different branch for any longer term experiments.
    You could use `wingo-git` in the AUR, but `go get` is just as good. (Indeed, the PKGBUILD uses `go get`!)
    One note those, use this to update to instead:
    go get -u github.com/BurntSushi/wingo
    go get -u github.com/BurntSushi/wingo/wingo-cmd
    You shouldn't have to delete any executables.
    As far as configuration files go... I'm not sure. I haven't figured out how I'm going to handle them yet. I don't think any well-formed configuration file will break Wingo, but it's certainly possible that old configuration files will miss out on new features/options. (For example, I just added some new focus follows mouse options.) Wingo will always maintain an in-memory default configuration, so missing configuration options will also never break Wingo.
    You can always check out the new configuration files by running `wingo --write-config`. You'll have to move `~/.config/wingo` to a temporary location first though.
    If you're installing from the AUR, I'll try to add post installation messages for any big changes.
    FYI, I should say that installation is so easy because of Go. :-) /plug
    Last edited by BurntSushi (2012-10-26 21:07:44)

  • I have Windows 7 with classic desktop display settings. My browser window is displaying in the system scheme, even though I have "Use system colors" unchecked and "Allow pages to choose their own colors..." checked.

    ''Duplicate post, continue here - [/questions/777317]''
    This is interfering with my browsing, as some text, images and links are obscured by the solid background. I could, of course, use the modern "Aero" theme but it would be much better to be able to use the display settings that I prefer.

    That's a painful example. I don't have access to Windows 8/8.1 myself, but I suspect this is by design, as I have seen other screenshots from users using high contrast dark themes that did not have background colors and images.
    Firefox 32 contains a change from this bug: [https://bugzilla.mozilla.org/show_bug.cgi?id=1042625 Bug 1042625 - Page should be drawn in accordance with the high contrast themes]. The testing (and a comment in the patch) refers to solving a problem on Windows 7, but apparently Windows 8 also was affected.
    I don't know whether there is a workaround to tweak what is and isn't displayed in the page with a high contrast theme.

  • License management with virtual machines

    Folks:
    We are using virtual machines.  If we have a staff change or a corrupted virtual machine, we create a new virtual machine by duplicating an existing hard drive, creating a new virtual machine, and assigning the duplicate hard drive to the new machine.  Works beautifully.
    The problem is that Acrobat thinks we have installed it on a new computer and therefore requires relicensing, and it won't re-license automatically because it thinks the license is in use already.
    Is there a way around this problem?
    Is there a way to convert our retail licenses to some kind of volume license where there is but one license code that can be used X number of times?
    Thanks.
    Micah

    I don't see such an option here: http://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/licensing.html?highlight=volu me.
    I don't think you can do that.
    Ben

  • Windows Server 2012 Pooled Virtual Desktop collection GetVMstate issue

    I am trying to create a Pooled Desktop collection with my Powered off VM and it errors out The
    virtual desktop must be in a stopped state:  Could not identify the state of the virtual desktop.  Ensure that the RD virtualisation host server is available on the network and the virtual desktop is shut down
    In the debug logs it shows.
    Component RdmsModel: GetVMstate for Vm Win7_BaseVM failed with error 16386
    Component RDExceptionHandler: Could not identify the state of the virtual desktop. Ensure that the RD Virtualization Host server sunflower-1.HYPERQA.NUTANIX.COM is available on the network and that the virtual
    desktop Win7VMSF is shut down.
    Please help on resolving this GetVMState issue.

    Hi Krishna,
    Thank you for posting in Windows Server Forum.
    When you are configuring RDVH initially, please see that you have meet prerequisites. Remember that you need these pre-requirements:
    • Database based on SQL Server 2008 R2
    • Static IP Address for all Broker
    • Round Robin DNS
    • All RD Broker must be members of AD Windows Group (es. RDCB Server Group)
    • The group must be insert into SQL Server as sysadmin ONLY for the DB creation. After that DB will be created give the db_owner permission only for their DB
    More information.
    Windows Server 2012 R2: Unable Add New VDI Template
    In addition, we need all RD Broker must have the same SQL Native Client as main SQL Server (es. SQL Server 2012 SP1). The Connection Broker server's computer account MUST be a member of the local administrators group on the Virtual Host (RDS Host) machine and
    then reboot the server. Finally check the result.
    Windows Server 2012 Virtual Desktop Template Issue
    Hope it helps!
    Thanks.
    Dharmesh Solanki

  • Desktop Environment VS Window Manager, what is the difference?

    I was wondering about the difference between DE and WM?
    It is just like iconize VS minimize or directory VS folder?
    So it is the same just more Unix-like or more Windows-like?
    Or there is a difference?

    Strictly speaking, a window manager is in charge of managing windows. It draws the decorations (usually just the title bar and borders) and places each window onscreen. It's also in charge of moving and resizing windows. If you run X without a window manager, each window opens, without a border, in the top-left corner of the screen (you can usually use the -geom or --geometry option to pick a default position when running an app), and you can't move or resize them. (Examples: Xmonad, evilwm, Metacity)
    Many window managers offer a built-in application launcher, usually by showing a menu when you right-click on the desktop. I prefer to call this a "desktop shell", what Enlightenment calls itself, because it does more than manage windows but is still a single program. (Examples: Fluxbox, Openbox, Window Maker)
    A desktop environment is a collection of programs and libraries designed to create an integrated environment. It almost always includes a window manager, with the notable exception of the RoX desktop. The individual parts of a DE can be swapped out if you prefer another program. For example, before XFCE included Thunar, I ran it with Openbox as a WM and RoX as a file manager. (Examples: KDE, XFCE, Étoilé)

  • Problem with Audio card in windows 7 in parallel desktop

    Hi my friends
    I was wondering if you help me
    I have a macbook pro ( mid 2010 ) MC374
    I installed windows 7 with Parallels Desktop but I haven't audio in windows 7
    What do I do to repair that ?
    thanks a lot

    Try installing the Cirrus driver from the BootCamp 4.0.4326 download:
    http://support.apple.com/kb/DL1636
    BootCamp/Drivers/Cirrus
    I read various things saying I should install the RealTek driver, but this didn't do me any good.  Two seconds after running the CirrusAudio32.exe, my speakers came to life.  Now Windows is dinging, chirping, and all that.
    This is on a MacBook Air A1369.
    -gjames

  • Follow-up: Enhancing multi-tasking in Windows 10 with the cloud

    This is a follow-up of:
    http://social.technet.microsoft.com/Forums/en-US/dbb2102f-00b7-47ca-88f2-4f88cd9d3409/followup-starting-launching-and-switching-?forum=WinPreview2014Feedback
    +
    http://social.technet.microsoft.com/Forums/en-US/eaf27b6f-68cf-4035-bfcf-6b37012bbfb2/eh-where-is-the-virtual-desktop-i-have-the-same-content-on-the-desktop-across-2-instances?forum=WinPreview2014Feedback#eaf27b6f-68cf-4035-bfcf-6b37012bbfb2
    + including some abstracts of http://social.technet.microsoft.com/Forums/en-US/0257e11e-35b0-4ff0-9a33-586d2edc60bc/if-youre-going-to-call-it-windows-10?forum=WinPreview2014Feedback#7d655548-51e3-4057-ac4c-b07ac0fe9064
    ... and assumes the above will be kind of implemented.
    Referencing that variable user software configuration above the virtual desktop can be dispatched and shared using both data and programs referencing for easy activation somewhere else.
    If you could mark the desktop itself as virtual - including the data being different across virtual desktops, the desktop could be loaded across multiple devices including apps - with Automatic installation of any universal Windows apps + suggestions
    for universal apps replacing a Windows legacy dekstop only app.
    In many ways a virtual desktop object would reference a user concept as probably a global object (i.e. would you have more than 2 video desktops in a consumer environment or more than 2 global video folders). The Apps list could also be like - working in
    context with virtual desktops.
    When the system installs it only has 1 instance of the virtual desktop - i.e. just a kind of legacy desktop. When you start using desktops - you can also do the "Move To" for programs and their concepts (i.e. program folders in all apps). Same
    goes for task bar + the Start Screen.
    In the SDK you would be able to enumerate the a virtual desktop object - i.e. its whole application including the context for user data and folders, applications, task bar and start screen configuration.

    Finally, for Windows 14 you could prepare task scheduling on the task bar for user work flows. I.e. for Windows dispatching a Word document including its virtual desktop for a class (example: can be used as a class room concept), especially
    now that Word, Excel are free for schools.
    It would be nice to have this in Windows 10.
    In Denmark this was already done a couple of years ago during HL/7 Projects with patient data in hospital care as an experiement in the town of Horsens. They added the extra functionality to the task bar in ... eh, was it Windows 7? (or was it before that).
    You could even suspend work.
    This would also allow for automated life cycle management of data in Windows. I.e. if some work are suspended you could use that to infer control of the data presentation in user namespaces.

  • SPLA & Virtual Desktops

    My goal here is to get feedback from other experts regarding Microsoft's current policy on Licensing Windows 7 as a virtual guest under SPLA licensing. 
    I am a consultant who encourages my small/medium business clients to seek out hosted remote office providers. In many cases, their core business applications do not work in Terminal server, Citrix, and PCoIP. There is a school of thought that virtually
    all of these problems can be overcome by modifications and workarounds, there are still some softwares that simply won't work. Also, sometimes the issue is not technical but rather licensing.  In summary, many software vendors simply won't provide support
    or allow for their software inside these environments. This is indisputable.  
    Nevertheless, many businesses that use "terminal unfriendly software" would still benefit immensely from a hosted virtual office solution.  One obvious option is to create virtual machines running an OS and configuration supported by the software vendor.
    This is less elegant, and less efficient (resource wise) than a simple terminal server configuration, however it would be supported which is critical.  It also carries several other advantages. 
    The bottom line is that Microsoft currently allows for this with windows licensing if the company does it in house. However, it specifically forbids that such a solution be hosted by a third party, as third party hosts are restricted specifically to the
    SPLA terms for virtualization hosting which is documented here.  
    http://download.microsoft.com/download/F/5/8/F58E786D-529D-438A-8625-4948205D8BA5/Windows_Hyper_V_Licensing_Whitepaper_v2_0.docx
    <quote>
    Scenario 5: Running Desktop Systems as Hyper-V Guests
    This scenario is currently not allowed under SPLA.
    </quote>
    Questions: 
    Does anyone else see the value in the virtual desktop model?
    Does anyone else see the value in having it hosted by a third party?
    Can anyone think of a reason why they would outright deny this functionality like this only for SPLA?
    Can anyone suggest a method for making a request to Microsoft to have this policy revisited?
    I understand that maybe it seems like a waste of time, and I do respect Microsoft's right to permit/deny the use of their software as they see fit. I just think they've specifically cut out a good idea and business model here, and basically said "If terminal
    server or citrix won't do it, then it won't be hosted in remote office (by a third party)".  I'd at least like to make my point and be heard. 
    Thanks for anyone who provides their opinion:
    -Jerry

    Below are copies of two emails l I sent in October 2010 to an individual at Microsoft who works directly with the Director of U.S. Licensing, who in turn reports to the VP of Operations that manages Volume Licensing for North America.  The ONLY response
    I've received to this and subsequent messages is that they're talking about it internally:
    <!-- [if gte mso 10]> <mce:style> <!-- [if gte mso 10]> <mce:style>
    October 2011:
    At the joint Microsoft/Citrix Virtualization Licensing webinar back on September 14, 2010, I asked about SPLA licensing for virtual Windows desktops hosted in an ITaaS model, and you said Microsoft has no plan on their licensing roadmap to provide for this. 
    You indicated in your brief response that you were unclear as to why this would be an issue. 
    It is, in fact, a critical and serious issue for ITaaS (HaaS/SaaS) providers – a business model that we are intent on implementing.  Please allow me to explain:
    At present, Microsoft SPLA licensing enables provider-hosted licensing for EVERY component of a Microsoft-centric SMB network environment
    EXCEPT the Windows desktop licenses .  VDA licensing (or Software Assurance added to Windows OEM, Retail or Open licenses) provides for CLIENT-OWNED VDI licensing, but
    makes no provision for provider-owned VDI licensing, and in fact, FORBIDS such licensing in a SPLA environment.   SPLA licensing forbids mixing with non-SPLA licensing, and yet no SPLA license EXISTS for virtual desktops.  Surely,
    you see how that leaves us stymied.                                       
    This is an impossible licensing disparity for ITaaS providers that leaves us, effectively “dead in the water.” 
    We can’t successfully implement a fully-hosted hardware/software environment WITHOUT virtual desktop licenses, yet Microsoft provides no way for us to implement such an environment WITH virtual desktop licenses!   If I’m missing
    something here, please let me know. 
    I understand that SPLA is the fastest-growing license category at Microsoft.  I can assure you that it would grow even faster if you make the rules consistent across your product line so that ITaaS providers aren’t having to figure out how to
    do magic in order to arrive at compliance with Microsoft’s arcane, self-contradictory licensing approach. 
    I and every other Microsoft Partner I’ve talked with about this (which is a sizeable number of Partners)
    are completely baffled by this situation , and we need some kind of intelligible response from Microsoft so we’ll know how to proceed .  This is now a pervasive topic of discussion among your Partners, so I hope
    you see it as important for Microsoft to address with something more than the “Here’s what you CAN’T do” responses we’ve gotten thus far.
    Here’s my question to you in a nutshell , and I would earnestly appreciate it if you would help me to get an answer from someone at Microsoft:                                                                                                                                                                                                    
    Does Microsoft have ANY license model or combination of license models that allows an ITaaS provider to do the following:
    1.     
    Host the Microsoft server-side products on equipment owned by the ITaaS provider
    (which is already straightforward to do with SPLA);
    2.     
    AND  AT THE SAME TIME, Host Windows Virtual Desktops and Microsoft Office running on equipment owned by the ITaaS provider.
    If not, is there any plan at Microsoft to make this possible.  And finally, if not, why not.
    I’m sending this follow-up to our emails from last week in an effort to further pin down some of the detail regarding the Microsoft licensing hurdles we’re encountering for fully-hosted ITaaS in Virtual Desktop environments.  If you can
    forward this internally in either HTML or Rich Text format, it’ll ensure that my colored highlighting is preserved (but I’m sure you already knew that!).
    I have no confidence that I’m reading and interpreting all the licensing requirements and restrictions exactly correctly, so I wanted to try to explain my own feeble understanding of those requirements and restrictions as they apply to the ITaaS scenario,
    and to let you and your team correct whatever I’m misunderstanding.
    But first, let me describe our objectives with regard to ITaaS
    – how this would work in a perfect world – so your team will understand as clearly as possible what we (and MANY other longstanding Microsoft Partners) are hoping to arrive at:                                                                          
    1.     
    We, the ITaaS provider, will own the server hardware infrastructure (a high-performance, highly-available server environment) and
    will locate the physical server-side equipment either at the client site (what we call Local Cloud Computing)
    or at an offsite data center .
    2.     
    We will “own” (be the license-holder for) all licensing for the Microsoft server operating systems and Microsoft server-side applications
    used by our customer’s end-users (e.g. Windows Server, SBS, Exchange, SQL,  SharePoint, etc.)
    and we will charge a predictable monthly fee to our customer for the use of this licensing . [I realize that software licensing isn’t technically “owned” by anyone other than the software creator, but allow me to use the term
    “own” for purposes of this discussion, so we’ll be clear about who holds the licenses.]
    3.     
    We will own all licensing for the Microsoft Desktop operating systems
    (e.g. Windows 7 Pro) and Microsoft client-side applications (e.g. Microsoft Office, etc.)
    and will charge a predictable monthly fee to the client for the use of these licenses.
    4.     
    We will host, and run on our server infrastructure, all the Desktop VMs accessed by our customer’s end-users .
    5.     
    The end-users will access the Desktop VMs hosted by us EITHER from existing PCs/laptops
    owned by the customer , OR from dedicated thin clients, PCs or laptops
    owned by us .   THIS IS WHERE IT GETS REALLY STICKY WITH MICROSOFT’S CURRENT LICENSING RESTRICTIONS, particularly SPLA restrictions about mixing license types in a given network environment.
    Over time, we expect that all existing PCs/laptops owned by the client will be replaced by thin clients, PCs and laptops
    owned by us , since the ultimate goal here is to convert everything to a hosted model.  But in the beginning, we expect that many of the desktop endpoints accessing hosted Desktop VMs will be PCs or laptops that are already in place and are
    owned by the end customer .  We can conceivably buy these existing devices from the client to arrive at a 100% provider-owned equipment model, but that will have some real challenges, especially where a given user’s primary device for accessing
    a VM is a handheld device (iPhone, iPAD, etc.) rather than a PC or laptop.  And it also creates an additional capital cost for us that will make it tougher to get an ITaaS approach in place.
    As I see it, a straightforward solution
    to the existing Microsoft Desktop VM licensing restrictions that would resolve all the issues above would be to create a true SPLA license for Desktop VMs, and to
    tie the SPLA VM license to the Desktop Virtual Machine itself rather than to a primary physical endpoint.  To my mind, what is making this whole thing
    so excessively complicated is Microsoft’s intransigent insistence on tying Desktop operating system licenses to PHYSICAL devices.
    Isn’t it time to truly open the door to a licensing approach that matches the reality of Virtualized operating systems by tying the OS licenses to the VMs?  Let the physical OSes (including
    embedded Windows for thin client terminals) be tied to the physical devices, and let the virtual OSes be tied to the VMs. 
    6.     
    We will provide comprehensive (all-in) managed services for our clients under this model, including troubleshooting and remediation, Help Desk, patch management, malware protection, and consulting.
    ALL of the above deliverables will be included as a predictable monthly fee to our customers .  Since Microsoft SPLA licensing includes constant eligibility for the latest versions of the Microsoft products (as well as downgrade
    rights for users that aren’t yet ready to move to latest versions), one of the huge business benefits to this ITaaS model will be “latest and greatest” versions of Microsoft product.  Because SPLA licensing and server/desktop virtualization
    make it so much easier to do software upgrades/migrations, we plan to also include labor for major version upgrades of Microsoft products within the monthly ITaaS fees paid to us by the customer.  We will also include scheduled hardware refreshes as part
    of the monthly fee paid to us by the customer under this model.
    That’s our vision – now we have to figure out how to make it work with Microsoft licensing, if at all possible.
    IF Microsoft allowed us to use SPLA for Windows 7 VMs accessed by desktop endpoints
    that WE OWN , that gives us one possible solution.  It would mean that if we want to let the end-users continue to use the PCs/laptops they currently have in place for accessing the Desktop VMs we’re hosting on our servers,
    we would have to BUY all of those end-customer’s user endpoints (PCs and laptops) in order to be able to be covered by SPLA for the VMs accessed by those machines.  That creates a financial hurdle in terms of our capital costs to
    implement ITaaS, but it’s not necessarily insurmountable.
    However, the problem with that scenario is that SPLA licensing presently
    includes specific prohibitions against MIXING SPLA licensing with other licensing models in the same environment
    .  So even if we DO BUY ALL the customer’s endpoint equipment AND we provide and own all the server equipment, we STILL can’t use SPLA licensing if there’s
    any other license type installed on any equipment in the environment.   This appears to be what the SPLA licensing says at this point, to the extent that I can understand it.  I’m anxious to be told that I have this wrong!  
    Again, it seems to me that ONE MODIFICATION would solve a multitude of different complications : 
    In effect, TIE THE DESKTOP WINDOWS VM LICENSE TO THE VM ITSELF, not to the endpoint device
    .   Since existing VDA licensing ALREADY allows for unlimited secondary endpoints (e.g. PDAs, traveling laptops, kiosks, etc.) to access a given VM, I don’t see where it materially
    changes the “spirit” of the licensing if you create a SPLA VM license and tie that license to the hosted VM itself rather than to the  primary physical endpoint.
    As things stand right now, this much is clear:  Microsoft currently
    considers the Desktop VM license to be tied to the primary physical
    ENDPOINT (Desktop device), NOT to the VM running on the server
    .  So the only way we can possibly use SPLA for Windows Desktop VMs is if WE OWN the actual Desktop devices along with all other Microsoft endpoints that run any version of Windows, Office, or any other MS software. 
    Again, I’m more than willing to be proven wrong about my assessment of the hurdles involved with Microsoft’s existing licensing options for hosted Desktop VMs!
    I remain hopeful that you’ll be able to get the right people involved at MS to identify one or more workable approaches for implementing a comprehensive ITaaS model, and if necessary, to modify SPLA licensing as it applies to hosted Desktop VMs so
    that it is simpler and more viable for ITaaS providers to cover all the bases.
    Please keep me posted on what you hear from your team.
    And thanks again so much for your assistance!

  • Win 2102: existing number of virtual desktops is not valid after errors while deleting , how to fix it ?

    Hello everyone,
    I created a virtual desktop collection with a name format like this , prefix = VDI-, suffix= 1 .
    so when I created the first VMs , I had VDI-1 and VDI-2 , later after recreating the VMs, adding new ones and deleting others, the suffix numbers are no longer in sequence , like I started having VDI-1,VDI-2,VDI-8,VDI-9.
    I realized I had one problem that probably caused this, because when I delete a VM , I get a warning message:
    "RD connection broker could not delete the computer account object from active directory."
    so I searched about that error and I added the needed permissions and now deleting seems to work without any warning.
    now I have two VMs, when I go through the wizard , the first page it shows I have 2 VMs but in the second page it shows I have 11 ! is there a way to reset the count ? if I delete the entire collection and create it again , will I have any problem with the
    roaming users profiles ?
    Thanks

    Hi,
    Thank you for your posting in Windows Server Forum.
    You can specify the count for RDVH as how many desktop wants for particular host. You can do this “Specify Virtual Desktop allocation” while creating virtual desktop collection. Other than that you can also use PowerShell command to achieve your task.
    For more details you can refer beneath article.
    1. Fumbling through Windows Server 2012 Virtual Desktop Infrastructure (VDI)
    2. Deploying VDI for RDS 2012 / 2012R2 – Part II – Publishing a Windows 7 Pooled Desktop
    Hope it helps!
    Thanks.
    Dharmesh Solanki

Maybe you are looking for