Spotify in locked down environment
-
Has anyone dealt with installing Spotify in a domain where the users are limited by policy?
I have a user that enjoys his Spotify and get a call at least once a week because there has been an update and it wants to install yet again.
-
You allow Spotify in a locked down environment?
What exactly are you trying to solve? What is the problem? His inability to update?
-
@Dashrender said:
You allow Spotify in a locked down environment?
What exactly are you trying to solve? What is the problem? His inability to update?
Spotify wants to be installed as the user using it. But even to run it after install sometimes it will ask for admin permission.
And of course right now it's failing to install with Errors 14 or 18.. even on a fresh boot.
-
You'll need to use something like ProcessMon to see what folders and registry entries are trying to be written to as a normal user, than give them rights to do so.
But really, this just proves the creators of this software don't follow standards and I wouldn't want that crap on my network if at all possible.
Please take your consumer junk and go home
-
I have plenty of users who might enjoy spotify at work, but that doesn't mean I'm going to let them have it. A "locked down" environment is meant to be just that... and I bet spotify works on his phone just fine.
-
There's an idea - since you're allowing him to use Spotify on your network, why not just add his phone to the WiFi, then let him stream through his personal device and then bluetooth to his own speaker? problem solved.
-
@Dashrender said:
There's an idea - since you're allowing him to use Spotify on your network, why not just add his phone to the WiFi, then let him stream through his personal device and then bluetooth to his own speaker? problem solved.
On the company WiFi??? HELL NO! That's why users have their own data plans....
"Not on my network..."
-
I thought the idea of a 'locked down' network was to stop this kind of useless consumer crap saturating your Internet connection and/or turning your firewall into Swiss cheese with all sorts of wonky ports open.
-
@RojoLoco said:
@Dashrender said:
There's an idea - since you're allowing him to use Spotify on your network, why not just add his phone to the WiFi, then let him stream through his personal device and then bluetooth to his own speaker? problem solved.
On the company WiFi??? HELL NO! That's why users have their own data plans....
"Not on my network..."
Not you - the OP. The OP was already allowing Spotify on the user's workstation, therefore they must be allowing it's use over the corporate network.
Moving the software to the user's device on their network should solve all problems. Actually it could be better, because now the OP could create a separate SSID/VLAN for the BOYD and limit it's bandwidth use so they don't have a problem on the production side.
-
Tell them to use the Spotify Web Player (https://play.spotify.com/). Then they don't need to install or update the Spotify client.
Having said that, the web player doesn't work on my PC. I think because I blocked it, but I can't remember how. The app works ok.
Alternatively, can't he just listen to music on Youtube like the rest of the world?
-
@Carnival-Boy said:
Alternatively, can't he just listen to music on his phone like the rest of the world?
FTFY
-
To be fair, the issue is not the OP's decision, but the decision of the owner of a remotely supported company. That owner wants everything locked down and secure, yet doesn't have an issue with this user having Spotify; therefore, we have to support him in "fixing" it every time it doesn't want to work. I think we all agree wholly that the entire thing is a dumb idea and a contradiction of policies, but if that's how they want it... (rolling eyes)
-
@art_of_shred The customer is not always right?
-
@dafyre said:
@art_of_shred The customer is not always right?
Got that right. Security and convenience are mutually exclusive.
-
Very seldom have I found the customer to be right, but that doesn't typically sway their decision-making outcomes.
-
This thread should go into the "1001 reasons not to be an MSP" book.
-
@RojoLoco said:
This thread should go into the "1001 reasons not to be an MSP" book.
Who is writing this book? I have about 1,000 more suggestions for entries!
-
@art_of_shred said:
@RojoLoco said:
This thread should go into the "1001 reasons not to be an MSP" book.
Who is writing this book? I have about 1,000 more suggestions for entries!
There will also be "1001 reasons not to work in educational/health care/non-profit IT" (each with its own book, obviously).
-
It could be an entire series! Kinda like the ___ for dummies books.
-
@art_of_shred said:
Who is writing this book? I have about 1,000 more suggestions for entries!
Probably the same person who was taking notes for me when you and I were speaking with the guy from DocuMation. A couple of points that came up in that conversation are no longer in active recall and I really did want to get them out of my head before this happened..
