gibbz

New Member
Joined
Mar 21, 2010
Messages
2
Id figure somewhere like here would be the best place to ask for this. Cant see any other problems like this in google, or search.

I have new PCs with Windows 7 Professional x64 and are trying to put them on the domain run through the server with Small Business Server 2003. The problem is that once connected through the domain everything on the desktop and through windows explorer is set as a hyperlink. I believe to fix this you have to change current user > software > microsoft > windows > currentversion > policies > explorer then set classicshell to zero in the registry. Is there anything I can do server side to solve this, its a bit of a pain to do for all the new computers and anyone else that wants to connect to the network on a PC with Win7.

If anyone has an idea ill try it when im back at work and post the results. I need this resolved pretty quick as these new computers need to be implemented.

Thank you.
 


Solution
It seems like you are experiencing an issue with Windows 7 Professional x64 computers that are being connected to a domain run through a Small Business Server 2003. The problem you described, where everything on the desktop and Windows Explorer appears as a hyperlink, typically indicates a registry setting that needs adjustment. The solution you mentioned about changing the registry setting for "classicshell" to zero in the path you specified (current user > software > microsoft > windows > currentversion > policies > explorer) is a valid way to address this issue on the client side. If you are looking for a server-side solution to prevent this problem from affecting new computers joining the network, you can consider Group Policy...
It seems like you are experiencing an issue with Windows 7 Professional x64 computers that are being connected to a domain run through a Small Business Server 2003. The problem you described, where everything on the desktop and Windows Explorer appears as a hyperlink, typically indicates a registry setting that needs adjustment. The solution you mentioned about changing the registry setting for "classicshell" to zero in the path you specified (current user > software > microsoft > windows > currentversion > policies > explorer) is a valid way to address this issue on the client side. If you are looking for a server-side solution to prevent this problem from affecting new computers joining the network, you can consider Group Policy settings. Group Policies can be configured on the server to apply specific settings to all computers that join the domain, which can help standardize the desktop environment and prevent issues like the one you are facing. To resolve this issue server-side using Group Policies, you can create a Group Policy Object (GPO) that sets the registry value classicshell to zero for all computers in the domain. Here's a general outline of the steps you can take: 1. Create a New Group Policy Object: - Open the Group Policy Management Console on your Small Business Server 2003. - Create a new GPO or edit an existing one that applies to all computers on the domain. 2. Edit Group Policy Settings: - Navigate to Computer Configuration > Preferences > Windows Settings > Registry. - Add a new registry item to set the classicshell value to zero in the specified registry key path. 3. Apply the Group Policy: - Link the GPO to the appropriate Organizational Unit (OU) or the domain root to apply it to all computers in the domain. By doing this, the Group Policy will enforce the correct registry settings on each computer that joins the domain, ensuring that the issue you mentioned with hyperlinks on the desktop and in Windows Explorer is resolved automatically for all new computers without the need for manual intervention on each machine. I recommend testing the Group Policy settings on a test computer before applying it to all production machines to ensure that it behaves as expected. If you have specific questions or need further assistance with configuring Group Policies on your Small Business Server 2003, feel free to ask for detailed instructions. Good luck with resolving this issue, and let me know if you need any more help!
 


Solution
Back
Top