DellOughta

Yeah, but its doesn't work all the time. Also this isn't a permanent fix more of a workaround (thanks though) Mike

Some of my users (randomly) experience a black screen at logon The setup up consists of 3 node cluster of server 2012 R2 remote desktop server (remote desktop session hosts in new money!!!) these are virtual hosted on hyperV, users connect through a gateway if coming in externally or straight via the connection brokers if connecting internally). Clients are W7 RDP version 8.1 I have tried numerous fixes such as enable \ disabling certain features with the RDP file enablecredsspsupport:i:0 bitmapcachepersistenable:i:0 Installing various patches including KB2887595 Deleting users profiles and starting a fresh profile CTRL ALT END killing windows explorer and starting fresh windows explorer (this doesn't always work for all users) Basically all the possible fixes listed here: Windows 2012: Rdp black screen on Windows Server - Grishbi Servers get rebooted every night Memory and CPU adequate Has anybody else got any fresh ideas on this one? Ta Mike

Used it before, sometimes servers that do work suddenly stop updating...its one of the many things I try to get updates working again Mike

try netsh winhttp import proxy source=ie Then run windows update Just had the same error myself, this fixed it :-) Cheers Mike

I have this working correctly in my environment, if you want we can set up a remote session and I can show you how I have done it (pm me if interested) Mike

Save your self the hassle, inform the users that you are creating a new standard corporate desktop (we have this in our place, different ones for different users) Just redirect the desktop to a share (give them read and execute rights) Create GPO as below and assign to the user group. Result = no files on desktop, no lost work, no long log on :-) Mike

Microsoft SyncToy is a good tool to sync /migrate files Download SyncToy 2.1 from Official Microsoft Download Center

As Michael says, you should be looking to create a .txt file looking something like this with all your users listed, then copy it all into a cmd prompt and run iCACLS F:\Students\yearof09\cowansrb01 /grant:r DOMAIN\bloggsf01:(OI)(CI)F /T /C

Besides the settings in your RDP file ref printers create a GPO Computer\Policies\Administrative Templates\Printers\Point and print Restrictions ENABLED That should let the users install drivers Also do you use a gateway server? might be worth checking that you have no connection policies blocking device redirection Mike

Looks like a different error to the windows 7 one and deffo related to internet explorer...cant remember the exact error off the top of my head. But the fix used in windows 7 was to edit the unattatended.xml find false and change to Reload the deployment share and bobs your uncle Mike

Hi These are the cmds I use to bulk create mailboxes for existing users (I use a spread sheet and create massive list of the same cmds with the different user names), I hide these users form the address book (only staff use the address book) I also give them a cu tdown version of outlook web access (don't want them faffing about stuff) CMD TO CREATE MAIL BOXES Enable-Mailbox -Identity DOMAIN_NAME\BLOGGS01 -Database EXDB01 CMD TO HIDE FROM ADDRESS LIST Set-Mailbox -Identity BLOGGS01 -HiddenFromAddressListsEnabled $true CMD TO APPLY CUT DOWN OUTLOOK POLICY Set-CASMailbox -Identity BLOGGS01 -OwaMailboxPolicy:STUDENTS_OWA Hope this helps Mike

GPO User Configuration\Administrative Templates\Windows Components\Windows Explorer\Hide these drives in My Computer [Restrict all drivers] User Configuration\Administrative Templates\Windows Components\Windows Explorer\Prevent access to drives from My Computer [Restrict A, B, C and D drivers only] The above settings are what we use in our environment achieves the restriction that require. Cheers Mike

For what its worth ours is a similar setup to yours FN-GM, users here also experience slow first login to OWA Mike

The reg key for running the updater on start up is here [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run] "SunJavaUpdateSched"="\"C:\\Program Files\\Common Files\\Java\\Java Update\\jusched.exe\" Create a GPO /reg delete to delete this key, then it can't run Mike

Try here Microsoft App-V 5: Installation and Configuration Using Windows Server 2012 and Windows 8! Part 1 Mike

Really good, easy to follow guide here Deploying Windows 8 Virtual Desktop Infrastructure on Windows Server 2012 ref installing hyper V / VDI on server 2012 Mike

Three parts to converting a fat client to thin and connect to a Remote Desktop/Terminal Server or VDI 1) Setup Folder and Files 2) Set auto logon for workstation 3) Create GPO to make it all work In this example it’s for connecting to VDI (just create an rdp file that suits your environment) Obviously I have tried to remove any user account details domain names etc but you should be able to get the gist of what’s required by following this guide. Setup Folder and Files Ok you’ll need a folder to locate 3 files so that they can be accessed by the auto logon user, we use: \\domain.name\netlogon\backgrounds\ The above was created historically before my time, but it can be anywhere The contents of this folder are 3 files (I’ll keep the names as they are in our environment but you can them what you want): VDI-111.htm VDI-111.rdp VDI-111.jpg Contents of: VDI-111.htm _________________________________________________________________________________ body { overflow:auto; } isNN = document.layers ? 1 : 0; function noContext(){return false;} function noClick(e){ if(isNN){ if(e.which > 1) {return false;} } else { if(event.button > 1){return false;} } } if(isNN){ document.captureEvents(Event.MOUSEDOWN); } document.oncontextmenu = noContext; document.onmousedown = noClick; document.onmouseup = noClick; blank.gif _________________________________________________________________________________ Contents of: VDI-111.jpg _________________________________________________________________________________ This is a simple JPEG that is presented as a wallpaper Create an RDP file This is the rdp file (its accessed when a user click on the jpg), in this example it connects to our virtual desktop pool for room 111 Tip: If your using VDI you can get all this information to put in your .rpd file from your connection broker in the server in the registry HKLM\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Terminal Server\CentralPublishedResources\Published Farms\ Just copy the contents of the above line REG_SZ RDPFileContents to a .txt file and rename as a .rdp This can be customised further, it’s up to you. Contents of: VDI-111.rdp _________________________________________________________________________________ redirectprinters:i:1 redirectcomports:i:0 redirectsmartcards:i:0 devicestoredirect:s:* drivestoredirect:s: redirectdrives:i:1 session bpp:i:32 prompt for credentials on client:i:1 server port:i:3389 allow font smoothing:i:1 promptcredentialonce:i:1 gatewayusagemethod:i:2 gatewaycredentialssource:i:0 use multimon:i:1 username:s:domain.name\ full address:s:.domain.name gatewayprofileusagemethod:i:1 videoplaybackmode:i:1 audiocapturemode:i:1 gatewayhostname:s:.domain.name workspace id:s:.domain.name use redirection server name:i:1 loadbalanceinfo:s:tsv://VMResource.1.W7-111-v1-1 screen mode id:i:2 desktopwidth:i:800 desktopheight:i:600 winposstr:s:0,3,0,0,800,600 compression:i:1 keyboardhook:i:2 connection type:i:2 displayconnectionbar:i:0 disable wallpaper:i:1 allow desktop composition:i:0 disable full window drag:i:1 disable menu anims:i:1 disable themes:i:0 disable cursor setting:i:0 bitmapcachepersistenable:i:1 audiomode:i:0 redirectclipboard:i:0 redirectposdevices:i:0 redirectdirectx:i:1 autoreconnection enabled:i:1 authentication level:i:2 prompt for credentials:i:0 negotiate security layer:i:1 remoteapplicationmode:i:0 alternate shell:s: shell working directory:s: _________________________________________________________________________________ The only things I have change in this screen shot is the server name and domain name domain.name everything else is as it. Test: within windows explorer open up the VDI-111.htm and double click the rdp icon, you receive the loon box and be connected to the server/VDI Set auto logon for workstation The next stage is to set up a user account make it auto login This can be applied by group policy or script or manually these are the settings and where they need to go (insert you user account and password and domain name) _________________________________________________________________________________ Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "DefaultUserName"="UserAccount" "ForceAutoLogon"="1" "DefaultPassword"="PASSWORD" "DefaultDomainName"="domain.name" "AutoAdminLogon"="1" _________________________________________________________________________________ Test: reboot your machines and make sure they autologon Create GPO to make it all work The final stage is to set up group Policy 1) Create and OU (in this example VDI_TEST)and put your workstations that you want to be thin clients in it, and create a group and the machines into it 2) Open GP Manager and create a GPO and assign to the group and to the OU 3) Add the following entry to User Configuration\Administrative Templates\System\Custom User Interface "%ProgramFiles%\Internet Explorer\iexplore.exe" -k \\domain.name\netlogon\backgrounds\VDI-111.htm Test: reboot your machines and make sure they receive the desktop, test double clicking on the icon and the user should be presented with the login box. Hope the above is easy enough to understand, msg me and I'll talk you through it if needed Mike

We use a simple set up on our site to convert fat client to thin client, user can then connect to VDI or Remote Desktop server and login (most of this is done in GPO for the client) and a directory on your network with the config files in. If your interested I can post details on how this achieved (its not too complicated) Mike

We had the same problem at our Academy (we've been using WDS \PXE Booting for over 3 years and some clever d1ck had spotted how we did it, so we had to lock it down somehow), the easiest way I found was to open WDS right click on the server node \properties\PXE Response and select the following Require administrator approval...... You can then go to the machine that you want to reimage, select F12 and get it to PXE Boot Pop back onto the server console, open WDS, go to the Pending Devices node (hit refresh) and you'll see your machine there waiting to be approved, right click approve and the image will continue. Mike

We are doing exactly the same as we speak...spooky!!! I'll let you know how we get on (were trying to do it with minimum downtime and currently only have one node of the original W2K8 R2 cluster hosting all the virtual servers, its man enough to handle them all), then using the same steps as you, clean build the other two, nics, etc, patch and add hyperV role and cluster feature, create a new cluster and then migrate from the old on a server one by one basis to new csv's, do a bit of stability testing with non business critical servers, then move the important ones over when were happy. There is a migration tool that comes with the 2012 failover cluster feature, we chose not to use that as we wanted to create a new cluster and do it peace meal Here's the guide Best practices for migration of cluster windows 2008 R2 / 2012 - As melhores Praticas para migrar um Cluster de Windows 2008 para Windows 2012 - War Room - notes from the field - Site Home - TechNet Blogs Cheers Mike

Set a GPO to change the guest.bmp and user.bmp located in C:\ProgramData\Microsoft\User Account Pictures To a similar sized .bmp of your choice/school logo. renamed as guest.bmp and user.bmp Mike

The beta service pack 1 that came out ages ago also gives you this message, worth checking to see if you've installed this by mistake Mike

syntax for shutdown NO REBOOT shutdown -s -m \\classpc1 REBOOT and FORCE NOW shutdown -r -m \\classpc1 /f -t 00 /f = force -t = time 00 = 0 secs

Thanks to a fellow forum member (Quince) I have a found an acceptable workaround/solution to this problem that is very easy to implement. In Frog Admin part where you make a network path available, instead of adding a network path, you add a small piece of html coding allowing widows explorer to be embedded in an iframe. (Sorry I’m not frog trained so might not have the correct terminology for the steps to take) In the above area in Frog Admin, delete the path that you originally had in the left hand pane. Then, simply DRAG a Text and Pictures Brick to the area where the old path used to visible (or a HTML Brick if its installed on your server) You should now see a highlighted box, it should say ‘Double Click to Add Text and / or Pictures’ Double click this new box, and you’ll be presented with the following screen, add the following piece of code (edited to your setup) (obviously the height and width and path can be changed to whatever you desire Or you could do it a folder share using the full path Then select the Strip Formatting icon You should now see something like this Save and publish this link, now users should be able to access the doc edit the doc and save it back in the location where it originally came from (providing all the correct rights are set on the share, and there’s no goofy group policies stopping). Cheers Mike

I've read on hear that frog live is supposed to solve this issue....how does it? I've installed it and get exactly the same results, is there some settings somewhere that need changing? Mike