WMS 2012 and Dell Wyse E01 zero clients

We have HP 6300 with Intel HD graphics. We are not able to start the server in normal mode. What graphic adapter can work together with Dell Wyse E01 ?

Yes we have used drivers version 12 and 13 but we can't trust them. Our solution is Radeon HD 6450 graphic adapter, Wyse driver version 11 on WMS 2011. This works very good.
So HP released a new computer. Deskpro 600 G1 with a new chipset. Then there is driverproblems again. We can put on 3 clients and it works, but when we connect the 4. or 5. client it won't work.
On WMS 2012 we have tried this:
Wyse driver version 13 for E01 and the built in graphic adapter Intel HD graphics 4600, but the screen resolution on the clients is wrong. On a screen like HP 2002LX we get a screen with 1024 X 768. 

Similar Messages

  • WMS 2012 and Touchscreen Support over Network Clients

    Hi all,
    I recently setup some virtual machines to operate with Dell Wyse E02 network clients. I purchased touch screen monitors to go with the zero clients, thinking that the E02's USB input would recognize the monitor as a keyboard and mouse. Upon testing the scenario,
    I found that the touch screen capabilities do not work.
    Is there anyway to configure WMS so that touch screens may be used over virtual desktops & network clients?
    Thank you so much in advance for the help! 

    Hi,
    For the multipoint server issue, I recommend you can post in the dedicated Forum for more efficient support:
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=windowsmultipointserver
    In addition, to install Windows MultiPoint Server 2012 Update Rollup 1, you can also download from here:
    Windows MultiPoint Server 2012 Update Rollup 1 (KB2791647)
    More detailed information about UR1, please refer to this article:
    Updating PCs and Virtual Desktops for Update Rollup 1 of Windows Multipoint Server 2012
    If there is anything else regarding this issue, please feel free to post back.
    Best Regards,
    Anna Wang

  • Unable to assign Wyse E02 Zero Client in Microsoft Multipoint Server 2012

    Hi
    I am implementing and lab classroom for 20 client to be connected on 2 HP Z230 workstation with Core i7, 16 GB RAM, 1 TB HDD. It will be 10 clients on each workstation.
    Everything is connected to a HP switch.
    I have sucesfull installed the Muitipoint Server 2012 and it is fully updated with latest Microsoft updates.
    I have also installed the Wyse E02 driver on the server so that I can view the station on Multipoint manager.
    On the "Network stations" tab,  I checked the box from the specific client and click on "Assign to this server". While processing I get the following error:
    Client Name: Network Zero Client
    IP: x.x.x.x
    MAC: xx:xx:xx:xx:xx:xx
    The network is busy. Please try again later.
    Thanks in advance for the support helping me to solve this issue.
    Regards.
    Muhammad A. Ismail

    So, my Wyse E02 eventually showed up in Multipoint Manager and I was able to assign it to the sever but it appears to constantly connect and disconnect. Most of the time now the client just shows the black screen stating "Waiting for assigned host.
    Ensure the assigned PC is running Windows Multipoint Server in station mode." Then I will see it disconnect and the screen will go to sleep and then will come back a few seconds later when MP Manager shows it reconnect.
    My Hyper-V server (which Multipoint Server is running on as a guest VM) is in the datacenter and my thin client is in my office for testing purposes.  I have them in the same vlan.  Is this not a supported configuration?  For a quick
    test I setup the Multipoint Server trial on a standalone OptiPlex and connected the Wyse terminal to the same 5 port Linksys switch and everything worked fine.
     

  • SCCM 2012 and old Wyse clients

    Hi,
    I'm fairly new to SCCM and I have taken over a network where they have deployed Wyse terminals using an image that has the Wyse System Center 2007 client installed.  However, WEDM was never deployed to managed those clients.
    I have setup a 2012 SP1 (CU3) CAS and DP and have successfully pushed out the 2012 client to desktops.  Unfortunately,, I can't seem to either get the 2007 terminals to register with this MP, or deploy the 2012 client to the terminal clients.
    Does anyone have any advice about how to do this?  - Or should I get each terminal (in the hundreds) re-imaged?
    Thanks in advance.
    Lee

    Perhaps I can create a shutdown script that disables the write filters and then restarts the machine.  - Then have a startup script that uninstalls the old client?
    Then I could run a batch script that restarts all of the terminals.  - Followed by installing the 2012 client via the ConfigMgr.  
    Lastly, I could push out a task sequence that updates the clients to CU3 and enables write filters.  Although, it seems VERY crude doing it this way! 
    I think you'll need to do something very like this, since you need to tackle the write filters for any changes to be persistent (unless there are WF exceptions for the necessary bits to allow persistence).
    It's been an awfully long time since I played with Wyse WinTerms, and much has surely changed.
    There used to be a heap of good information on the Wyse website, back in the day?
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • WMS 2012 with WYSE EO2 clients requires UR1?

    Hi, I'm currently int he process of updating my Evaluation version of Multipoint 2012 via Windows Update.I was going through the release notes of the latest driver for my zero client WYSE EO2. It states -"Using Windows Update Manager, download and
    install latest Windows updates to the system. (Highly recommend). Install Windows UR1-From Windows update. Windows Update Manager should automatically install all the latest patches, including this one. (Highly recommend)."
    Ive also read through the installation instructions for the server. My questions are -
    1) Is the UR1 update a part of the automatic updates?
    2) I was having problems with the video display on a work station connected to the server via WYSE in my earlier attempts at setting up the server client network. Are these latest updates expected to solve that problem?
    3) Is there anything regarding the updates that I should consider/pay attention to?

    Hi,
    For the multipoint server issue, I recommend you can post in the dedicated Forum for more efficient support:
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=windowsmultipointserver
    In addition, to install Windows MultiPoint Server 2012 Update Rollup 1, you can also download from here:
    Windows MultiPoint Server 2012 Update Rollup 1 (KB2791647)
    More detailed information about UR1, please refer to this article:
    Updating PCs and Virtual Desktops for Update Rollup 1 of Windows Multipoint Server 2012
    If there is anything else regarding this issue, please feel free to post back.
    Best Regards,
    Anna Wang

  • Unable to record on my Thin Client on WMS 2012.

    I really need help here, I have up to 65 thin clients and 4 vm running WMS 2012 on WS 2008 R2 and they are all licensed. The issue is this, on the clients, i am unable to record. Its not detecting the Headphones mic, but it could speak out with the headphone-speaker
    and i am confused right now. I need help. May God bless every one reading and replying this to help me solve this issue.Amen.Thanks

    Hi Philippe,
    I really appreciate your effort. I don't understand the gear in your response saying with certified driver and such and using the same gear with a windows laptop/com... to rule out the thin client firmware, Please can you  explain a little bit with
    basics. For the firmware update i will try it in one of it. Thanks, will be expecting a feedback from you and anyone else can also comment. I want to be sure of the firmware thin before making any changes because when doing any firmware upgrade/update, someone
    needs to be careful.
    Regards,
    Kunle.

  • SCCM 2012 and 2012 sp1 client cache not cleaning itself

    I work on a University campus that deploys 100's of software titles to lab computers.  Since last summer, we have been using Config Man 2012 and upgraded to 2012 SP1 in early Jan.  Recently we started noticing 160GB hard drives filling up in locations
    that get most of our software.  When looking into it, the ccmcache folder has 50GB+ of data in it even though the cache size is set to 30GB.  I looked at the folders in the cache and many of them are from last summer when the apps were first
    downloaded and installed.  NONE of these apps are set to persist.  My understanding is that they should have been cleaned up automatically after 24 hours as space was needed.  Either way, shouldn't the cache folder be at or smaller than the
    cache size setting? 
    I have talked to others that have seen similar problems with 2012 of the cache folder growing beyond the max, but they don't have the software load that we do, so they are not filling their drives.  If I manually tell Confi Man client to delete the
    cache files, I free up 50GB or more, but manual intervention isn't a great option.
    Any ideas on where to troubleshoot this issue or what settings might be messed up that allows for this?
    Thanks

    How much of this is software updates?  Like in 2007 software updates are not counted against the cache size:
    "You can configure the location and amount of disk space that Windows Configuration Manager clients use to store temporary files for when they install applications and programs. Software updates also use the client cache, but software updates
    are not restricted by the configured cache size and will always attempt to download to the cache"
    https://technet.microsoft.com/en-us/library/gg712288.aspx
    http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

  • Anyone using VXC zero client with IP Communicator, UCCX and AQM?

    Wanted get gauge of if running Virtual desktop using VXC zero clients will work replacing our desktop recording for our call center.

    There are some known issues like one -way or no voice being heard only while using VPN. Check the following link http://www.cisco.com/en/US/partner/products/sw/voicesw/ps5475/prod_release_note09186a008043a3ba.html for known issues. But in this case I would suggest you to upgrade the VPN client software

  • SCOM 2012 and NAP 802.1X Enforcement - Event ID: 6276 during client startup - False positive

    Hi
    We are running SCOM 2012 and we are using NAP 802.1X enforcement with HP IDM. We are getting multiple event ID: 6276's entries in SCOM during computer start-up, which is false positives as it seems the computer is put into the Non-Compliant network until
    its true state is reported. Is there a way to suspend these events, in order for us to only receive valid Non-Compliant events?
    Regards, Francois
    Francois Vorster

    Hi,
    You can make dot3svc dependent on NAP agent so that NAP agent starts up completely before the first 802.1X authentication attempt is tried. This should reduce the number of re-authentication attempts.
    -Greg

  • HP t410 Smart Zero Client display lag

    Hello there
    This is my first question in the HP forum, we are using HP t410 Smart Zero Client in our network, the clients use it to connect to diffrent Windows Desktop Services Servers on windows 2008 R2 over RDP 7.0 protocole in some cases it is Windows 2012 Server & RDP 8.0 protocols now the problem is that there is considerable amount to lag or choppiness when scrolling documents and webpages this is extreamly painful for users.
    Now this is not the case with when i try connecting via a laptop or desktop windows remote desktop tool or some old WYSE thin clients.  i am betting that this is some configuration issue which can be overcomed. can someone please help me out ? we are just using these HP t410 Smart Zero Clients out of the box, no configurations were done on nighter clients nor server sides.
    regards
    Faisal Gillani
    Preview

    Hello ski_mike.
    Welcome to the HP Forums. I understand you would like assistance with your Smart Zero Client. However, this is a commercial product. To get better assistance, please post your issue on the HP Commercial Forums: HP Enterprise Business Community
    Thanks,
    Mario
    I worked on behalf of HP.

  • MDT 2013, Deploying Windows 8.1 on Surface and Dell Venue Tablets

    I'm having numerous issues with Capturing Images and Deploying to Windows 8.1 Tablets. We are currently using Surface Pro 1, 2, and Dell Venue 11 Pro tablets. I am using a Windows Server 2012 computer with MDT 2013 installed. I can't get the tablets
    to:
    1-sysprep and capture using MDT 2013
    2-Deploy a Task Sequence with a WIM and other applications attached. (I've tried using the simple standard task seq option with no luck)
    3-I found another way to get a WIM (using imagex) but when i deploy task sequence it ignores my selection of applications to install outside the WIM and only installs the WIM (WIM 14gb = Win 8.1 Ent, Office 2013 x32, MS Updates)
    Any help would be greatly appreciated. Everything is being performed within the LAN and with USB 2.0 thumbdrives for media.

    Hi altimav8,
    Are you trying to find out how to deploy Surface Pro method? Before capture the Surface pro image please download the latest drivers for the surface and made sure that they
    were the only drivers that were going to be deployed. There have a specific MDT deploy support forum more about the MDT deploy related issue you can ask in MDT support forum.
    MDT support 
    forum:
    https://social.technet.microsoft.com/Forums/en-US/home?forum=mdt
    The related guide:
    Surface Pro - Enterprise Deployment Quick Start Guide
    http://download.microsoft.com/download/2/0/7/2073C22F-2F31-4F4A-8059-E54C91C564A9/Surface%20Pro%20-%20Enterprise%20Deployment%20Quick%20Start%20Guide.pdf
    Thanks for your understanding and support
    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.

  • Windows server 2012 and windows 7 direct access

    I am looking for some decent documentation on how to get direct access in windows 2012 to work with windows 7
    Can anyone point me the right direction?

    Hi, I got success through this
    http://syscomlab.blog.com/2012/09/how-to-get-windows-7-to-work-with-directaccess-server-2012/ and this one
    http://syscomlab.blog.com/2012/09/directaccess-for-windows-server-2012-guide/ but I'm using NLS in a dedicated server (what is fine for me) but the Win7 client doesn't connect to DA (EDGE server) through internet. I'm using a LAB where WS2012 host acts
    as a GATEWAY (using NAT) and for Windows 8 client is working fine but when I try using win7 clients it just doesn't work :(
    Server WS 2012 RTM full patched + Win8 Enterprise RTM full patched + Win7 Enterprise RTM ful patched (including the recommended KBs for DA solution)
    regards,
    Thiago
    Thiago Beier Se foi útil marca como resposta! Don´t forget to mark as answer!

  • Server 2012 and 2012 R2 do not allow access to all 7 optical SAS drives?

    The following problem occurs with Windows Server 2008 R2, 2012 and 2012 R2, Datacenter or Standard. 
    I have an external SAS enclosure with seven optical drives and one hot-swap SAS/SATA bay that connects using two SFF-8088 connectors (no internal SAS expander, etc.).  The purpose is to use the seven bluray writers to write multiple copies of a large
    database simultaneously.  The optical drives are also occasionally used to read datasets that come on multiple discs (usually 8-12 per dataset and up to 15 datasets at a time).  Because of the volume, more optical drives are definitely better. 
    Regardless of the type of SAS controller used to connect this enclosure, some significant functionality is always missing.
    For writing, it is best to connect directly to the optical drives (which do their own buffering) so a HBA would seem better than a hardware RAID controller.  I have tried several HBAs, including LSI-9211, LSI-9240-IT, Dell H310-IT.  In all cases,
    Windows only sees four DVD drives and the hot-swap bay.  The drives Windows sees work perfectly for reading and writing.  MegaRAID Storage Manager (LSI controller software) sees all seven optical drives and the hot-swap bay.  LSI says this
    must be a Windows problem.  Strangely, if I remove (any) three optical drives and replace them with hot-swap bays, all eight devices are recognized by Windows.
    If I use a true RAID controller (tried LSI-9260, Dell H800, Dell H810, HP 812P, IBM 5015), windows and MSM see all seven drives and the hot-swap bay, reads from the optical drives are fine, but writing large discs times out (presumably because of buffering
    by the RAID card) so I can't write DVDs.
    Is there a way to get Server to recognize all seven optical drives on an HBA?  Ideally, I'd like to add several of these enclosures but I can't even get one working properly!
    The system is a Tyan (Dell) MB with dual Xeon E5-2620s and 64Gb RDIMM.  Currently includes LSI-9260 (2Tb SAS 10k in RAID 0), Dell H810 (32Tb SAS in RAID 6), and LSI-9211 (optical enclosure + 3Tb hot-swap).  Just installed Server 2012 R2 Datacenter
    for testing.
    Any help would be greatly appreciated.

    I've had the experience of working as a validation engineer for Intel, who at the time was developing a SAS/SATA storage controller chipset for thier new xeon processors. The chipset was included in their motherboard offerings. I validated the linux driver,
    which is now included in the linux kernel as of the 3.x series kernel.
    My first question is, what type of SAS enclosure are you using for your optical drives/hot swap bay? You will be surprised at how many enclosures don't actually provide a 100% direct-attached storage configuration, and instead opt to work as a mini expander
    instead. In our validation, we tested several SAS enclosures, and we found several that even though they were advertised as direct-attached enclosures, by inspecting the data transmission with a SAS protocol analyzer we found communication over SMP (Serial
    Management Protocol).
    To ensure it is NOT the enclosure causing the anomaly, i'd connect the 7 optical drives directly to each storage controller unit (or sff-8087). These cards can support around 256 devices via expander attached configuration, as that is how many sas addresses
    the scu's can support. Either way, they can only support a maximum of 8 devices direct-attached (4 per SCU). I would use a multi-line SFF-8087 SATA breakout cable to directly connect your optical drives to the HBA, 4 on SCU0 and the other 3 on SCU1.
    I find it strange that LSI's storage manager can see all of the drives, but windows cannot. Since the SAS protocol allows for the ATAPI cmd set to be sent via scsi commands, the only thing I can think of is if windows can only recognize a certain amount
    of SAS-addresses utilizing the ATAPI cmd set. Technically, it should only be limited by the number of devices the hba can support, and in either LSI thats 256. Otherwise the enclosure may be doing something funny with the initiator (SCU), where one initiator
    may take precedence over the other. Again, testing a direct connection with a SFF-8087 SATA breakout cable will eliminate the enclosure as a factor.
    I can understand from a developer perspective for the desire to have windows recognize the devices instead of relying on the lsi storage app. Firstly, that app is monstrous and unwieldy. Secondly, it does not allow for customized solutions/scripting to fully
    access the optical devices, since you have to interact w/ lsi's storage mgr. 3rd, this should simply work if MS is fully compliant with the SAS protocol.
    Finally, I want to make sure everyone is aware that a fully compliant 6G SAS compliant device will support SSP (Serial SCSI protocol), SMP (Serial Management Protocol), and STP (Sata Tunneling Protocol). STP basically defines how SATA devices can inter-operate
    within the sas fabric by tunneling ATA commands via the SCSI cmd set. This is a basic functionality guaranteed within the overall SAS protocol; if your HBA supports SAS & SATA, it will support SSP, SMP, and STP frames (this is usually always listed on
    the HBA), and therefore it will fully support SATA devices. A SAS device will support SSP & SMP. A SATA-only HBA will support the ATA cmd set only (and thus, cannot inter-operate within a SAS fabric).
    Please note that at the very least, a direct-attached configuration should provide the number of Storage Controller Units x 4 fully working SATA devices (generally each internal SFF-8087 is a scu, most HBA's have a min of 2 SCU's, and 4 directly addressable
    devices per SCU (8 direct attached devices total). Generally, any issues that will arise from SATA devices will be the result of expander-attached configurations. There are many points a SATA device can experience errors in a expander-attached configuration,
    from the routing mechanism being utilized (table vs subtractive), to the type of expander being used (fan-out vs edge expander). Expanders will generally at least support 1 method of routing, if not both, and may or may not support multi-level configurations
    (this is specifically dependent on the hba). It was not uncommon in our testing to come across expanders that would work great w/ SAS & SATA w/ 1 level expander, but fail to communicate with SATA devices past 2 or more levels. This falls on the responsibility
    of the HBA, specifically the driver for the OS.
    More Info on SATA Tunneling Protocol (STP): 
    http://www.serialstoragewire.net/Articles/2004_0225/developer_article_2_feb.html

  • RemoteApp 2012 and File Type Associations

    Hi, All :),
    the scenario is like this -  2 x Server 2012: one as the RD Connection Broker and RD Web Access and one as the RD Session Host (clients are Windows 7). ALMOST everything works: there is one collection, several applications, all successfully thrown into
    the RemoteApp and Desktop Collections by GPO (Powershell script - http://gallery.technet.microsoft.com/ScriptCenter/313a95b3-a698-4bb0-9ed6-d89a47eacc72/).
    But one thing doesn't work - file type associations. Well, I want the client without, for example, Office installed to open the RemoteApp application (Excel) by clicking on the XLSX file. When looking at the application properties -> File Type Associations
    -> Current Associations column, I see the name of the collection, which includes Excel ... but it does not work. After updating the RemoteApp and Desktop Connections on the client, the RDP file with Excel noticed a new line:
    remoteapplicationfileextensions: s:. csv,. xls,. xlsx,. xltx
    How do I make it work? I know that in RemoteApp on Server 2008R2 you could export the MSI file that took care of File Type Associations, but what to do in case of Server 2012?

    Unfortunately, the feature to install file type associations for RemoteApp programs in your GPO-pushed RemoteApp and Desktop Collection is only supported on Windows 8 clients. Several improvement were made over the old MSI-based file type associations, and
    those improvements rely upon changes in the Windows 8 OS.
    Ultimately file type associations are controlled with registry keys, all of which are documented on MSDN. RemoteApp programs are pretty much the same as any other local program, except the file type is associated with mstsc.exe with some special parameters.
    Although the way we register those file type associations in Windows 8 won't work for you, the way the old MSIs used to register them would. You could in theory register the RemoteApp file type associations yourself in the same way that one of the old MSIs
    would have done (you could use some sort of GPO-pushed script on the clients).
    The easiest way to do this would be to track down one of those old MSIs, install it, and do a before-and-after view of the registry to see what changes it makes.
    Hope that helps,
    Travis Howe | RDS Blog: http://blogs.msdn.com/rds/default.aspx

  • SCCM 2012 on Server 2012 and WSUS 3.0 SP2 on Server 2008

    We are installing SCCM 2012 SP1 fresh into our development environment - the primary site server and the database (SQL 2012) are both being installed on Server 2012.
    We have an existing WSUS box on a Windows 2008 (not R2) server - the WSUS server version is 3.2.7600.256.  We have set this up as the software update point.
    For the purposes of this discussion, these are the server names (obviously obfuscated):
    Primary site server:  sccm.domain.local
    Database server:  sccmdb.domain.local
    WSUS server:  wsus.domain.local
    On the primary SCCM server, I've installed the WSUS user interface (Install-WindowsFeature -Name UpdateServices-UI), in order to work with the remote WSUS server.
    Updates synchronization appears to be working fine, but when I try to setup client distribution via SUP, I'm getting the following error in the Application event log:
    Log Name:      Application
    Source:        SMS Server
    Date:          8/6/2013 11:03:11 AM
    Event ID:      6613
    Task Category: SMS_WSUS_CONFIGURATION_MANAGER
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      sccm.domain.local
    Description:
    On 8/6/2013 11:03:11 AM, component SMS_WSUS_CONFIGURATION_MANAGER on computer sccm.domain.local reported:  WSUS Configuration Manager failed to publish client boot-strapper package "9D5353E5-DA80-48C3-97DE-C9C528F73A2D" with version "5.00.7804.1000"
    to the Software Updates Point.
    As well as this in the WMC.log:
    PublishApplication(9D5353E5-DA80-48C3-97DE-C9C528F73A2D) failed with error System.InvalidOperationException: Publishing operation failed because the console and remote server versions do not match.~~   at Microsoft.UpdateServices.Internal.BaseApi.Publisher.LoadPackageMetadata(String
    sdpFile)~~   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetPublisher(String sdpFile)~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.PublishApplication(String sPackageId, String sSDPFile, String sCabFile)  $$<SMS_WSUS_CONFIGURATION_MANAGER><08-06-2013
    11:03:11.787+240><thread=3704 (0xE78)>
    ERROR: Failed to publish sms client to WSUS, error = 0x80131509  $$<SMS_WSUS_CONFIGURATION_MANAGER><08-06-2013 11:03:11.803+240><thread=3704 (0xE78)>
    It would seem obvious that this is because of a mismatch in versions between the WSUS server version on wsus.domain.local, compared to the UpdateServices UI on sccm.domain.local.
    Is there a way around this, without having to upgrade the WSUS server to Server 2012?
    Thanks for any thoughts you may have!

    Not really. As mentioned though, even the separate WSUS server is probably overkill. In ConfigMgr, WSUS is used to handle the update catalog and that's it. Clients do *not* report status to the WSUS instance and do *not* download updates from the WSUS instance.
    No management is ever done in WSUS.
    So, in reality, once a month, clients connect to WSUS to download the delta update catalog (delta compared to what they currently have) which usually comes out to about a few hundred KB (yes KB, not MB) -- this download is done via BITS. The server also
    syncs the catalog from the WSUS instance, via the SUP, in a similar fashion. If you are using SCEP, the frequency will be greater, but the deltas will be much smaller.
    EULAs, as needed, are also stored in WSUS and accessed by clients -- these are also quite small only a select few updates requires them.
    That's it. Standing up a dedicated WSUS instance means having a server sitting there doing almost nothing else.
    If you are concerned about load on the site server, then you should create a separate site system that contains the MP, SUP (and WSUS instance), and DP. Then, for HA purposes, you can simply build a second site system with these three roles also and HA will
    essentially be automatic (from a client functionality perspective).
    Jason | http://blog.configmgrftw.com

Maybe you are looking for