macdaddy

@ADMaster You sir are Brilliant! Copied the "First Run" file from an existing profile that has logged into Chrome and pasted to your location mentioned. Had to create the subfolders in the process. Now just need to add this as a task in SCCM and off and running. It does appear 1607 made changes, a shame Google was not on top of this.

@rogerdnixon thanks for the idea but we already do this. I am beginning to think this problem is Windows 10. The same problem with Chrome Welcome page also occurs with Edge. IE works fine. Both Chrome and Edge are controlled by Group Policy to stop the welcome page. I believe the issue maybe that the registry keys needed to suppress the welcome page are not created until the user first launches the browser. This link touches on the subject. I have tried adding the powershell script during imaging with SCCM but did not work. Need to test this further.

We employ Group Policy to set Chrome Home Page and to suppress the Welcome page. For years this has worked great on Windows 7 Pro machines. The result is with a user logging in the first time and opening Chrome they only get their Home Page tab. We are now deploying Windows 10 Edu 1607 and Chrome with first time user gets the Welcome to Chrome tab and their Home Page tab. Has anyone else seen this issue? OS=Windows 10 Edu 1607 Chrome=v57 Using the latest admx and adml files in central store

This worked perfectly for us. We used SCCM 2012 to push out to a lab of 25 desktops. Many thanks to Kris! The App Inventor 2.zip file was empty, after PM'ing Kris he quickly sent the file. Again many thanks saved us a lot of time!

We have moved all staff/students files from 2003 R2 servers to 2008 R2 making the adjustments below and working fine. 1. Manually create a "My Documents" subfolder in the user's home folder. Maybe someone has a script to do this. 2. Move all files into the sub folder. 3. Delete the desktop.ini file at the root of the users home folder. NOTE: This can be tricky on 2008 R2. The "ownership" will mess things up. More steps to take ownership and delete. If scripted much easier. 4. The folder redirect will point to the sub folder. exp=\\servername\share\%USERNAME%\My Documents Since implementing this we have had no issues. Yes it took a lot of work but this is the permanent fix to the issue. I do not see M$ changing this as they see this to be correct 'by design'. Also to check permissions and verify the 'desktop.ini' file does not mess you up use the NTFSFix tool which you can find at WiseSoft - Resources for IT Professionals. This is a creat tool to update/change/add permissions quickly. Bob Systems Specialist

The real problem is when you redirect the user to their home folder Windows 7 by default turns on synchronization. This then rewrites the "desktop.ini" file in the home folder. To correct this we added a new Group Policy, attached is the settings.

We have used this for the last two months now and have had no problems. For us the GP is placed in the "Computers" OU which houses desktops and laptops. We have a mix of XP and 7. Since implementing this we have had no synchronization. But keep in mind for us we wanted to implement this District wide. We have not seen the home folders effected as well so there is no "renaming" of the home folders as before.

[quote=Anyone have any ideas or see anything I've missed? Cheers James On the new print server did you go into Print manager and deploy the printer via policy?

Another method is as follows: You need to go to a 32-bit Vista/win 7 workstation Start\run> \\Printserver and display your shared printers. Double click a printer & wait for it to install. After it installs on the workstation go into the local printers, right click on the network printer you just installed. Select printer properties, sharing, additional drivers and select the x86 box. Click OK and the x86 drivers should upload to the server. I find this to be the easiest method. I also find the universal drivers to work the best.

Yup we just ran into this also. The problem was our win 7/XP was 32-bit. 2008R2 is only 64-bit. You will need to add 32-bit print drivers to your 2008 R2. The "universal" drivers work best.

It would appear this is one of those M$ features. Doing further testing it would appear SYNACK's original post does work. He referenced this link [solution]: Mapping printers with logon scripts in Vista&7 without UAC interupting The mistake I made was the policy had computer disabled which is essential for windows 7. So thank you everyone for the assist. For us ramping our print servers to 2008 R2 was not cost prohibitive.

We also are experiencing this problem. Problem is with users in the users group such as students. What we have found is from a 2003 print server this occurs. From a 2008 R2 print server it is fine. I have not tested on 2008 R1. If I push the printers via Group Policy it is fine. From the forums I have read Microsoft is aware of the problem but has no solutions.

Discovered on Windows 7 and students (user) are logged in and they try to install a printer the "UAC" comes up looking for Admin credentials to install. We are using Active Directory with 2003 DC's and Print Servers. Everything works fine with Windows XP. If we "push" the printer via Group Policy it installs fine. If we add a Windows 2008 R2 Print Server adding 32 bit drivers the Windows 7 (32 bit) will install the printer for the user. I have looked in all the forums and cannot find the answer to this problem. HELP!

That is exactly how we started out. Since then we have expanded the GP's by using WMI Filtering and under Preferences using Item-Level Targeting to streamline the process. For example instead of making an OU just for Windows 7 computers/users simply use the WMI Filter to apply to just XP and to just Windows 7. Item-Level Targeting can also be used for this fine tuning as well. For example we have a shortcut for Word on the student desktops. Problem is the computer may have either version 2003 or 2007. By using Item-Level Targeting we created a shortcut for word 2003 and a second one for 2007 in the same GP. One problem with Windows 7 has been the desktop background which when loaded is a black background. With the new powerful tool of Preferences a registry change can be made without creating a script. Another example of the "suttle" changes is in 7 the redirect folder is called "Documents". The 'local documents is tagged by the users name in the Start Menu. We have adjusted the GPO's so only the redirect "Documents" shows up making it less confusing for the user. As you can see with the new Windows 7/2008 R2 GPMC it is more powerful and much more user friendly to the IT personnel.

You also may want to look into WMI Filter. I use it to apply with different OS's. Since we are running XP/7/2008 TS/2008 R2 TS the student policies are all slightly different. By using WMI Filter I have multiple policies but one OU.