Microsoft's decision to not allow the name of the homegroup to be changes has got to rank among the poorest ever. I have only one windows 7 machine and it would be far easier to place it in my multi-machine group than it will be if I have to change all of the other machines. This for me is a huge waste of time and effort that could be more productively used. I also think that this is an open season call to hackers. My internal group has a name that is not common to every other machine in the world using the operating systems I'm using. This is another case of Microsoft doing what makes the most money instead of what is best for the user. Linux keeps looking better and better.
📎 AI Summary:
The thread discusses frustration with Windows 7's inability to change the homegroup name, with the original poster criticizing this as a poor decision that complicates network management and raises security concerns. A responder shares a workaround by disabling the homegroup and reverting to the traditional workgroup method, finding it more straightforward. Overall, the sentiment reflects dissatisfaction with Microsoft's approach and a preference for alternative networking options.
The thread discusses frustration with Windows 7's inability to change the homegroup name, with the original poster criticizing this as a poor decision that complicates network management and raises security concerns. A responder shares a workaround by disabling the homegroup and reverting to the traditional workgroup method, finding it more straightforward. Overall, the sentiment reflects dissatisfaction with Microsoft's approach and a preference for alternative networking options.
Highwayman
Extraordinary Member
personally I just disabled homegroup and went back to the old workgroup n accounts method, works better and none of the faff on.
