This message was deleted.
# microsoft-fslogixs
Slackbot
09/16/2019, 7:27 PMThis message was deleted.
👍 2
l
Leee Jeffries
09/16/2019, 7:28 PMNice one Nick. Lol , it's always a sneaky GPO!
b
Biny
09/16/2019, 7:29 PMwhen it's not that, it's dns!
l
Leee Jeffries
09/16/2019, 7:30 PMYes it is!
n
Nick Panaccio
09/16/2019, 9:19 PMSo... user error? ;)
n
Nick Casagrande
09/16/2019, 9:27 PMWell mine.
n
Nick Panaccio
09/16/2019, 9:30 PMYou’re supposed to blame it on the VMware guys...
n
Nick Casagrande
09/16/2019, 9:49 PMHehe. I am the vmw guy too.
j
James Kindon
09/24/2019, 5:21 AMhey @Nick Casagrande isn't that policy for Server 2003 only? I am on site staring at the same policy wondering if i should kill it or not?
n
Nick Casagrande
09/24/2019, 11:33 AMnope, all of my servers are 16/19 and vdi vm's are w10 1809 ltsc
j
James Kindon
09/24/2019, 11:36 AMWeird - description says 2003 only - maybe ms never updated the text 😳 what did you set it to in the end?
n
Nick Casagrande
09/24/2019, 11:48 AMnot config'd i just removed it. for some reason i set it to disabled years and years ago when we did vdi for xp
Nick Casagrande
09/24/2019, 11:49 AMfrom what i could tell, v4 printer drivers must have something to do with kernel mode as it was all of my v4 drivers that were causing my issues, v3's were fine. perhaps b/c fslogix is also a kernel mode driver? who knows...
j
James Kindon
09/24/2019, 11:50 AMI found it in the default domain policy today 🤦♂️🤦♂️🤦♂️🤦♂️
James Kindon
09/24/2019, 11:51 AMGlad you shared as it flagged instantly so cheers
n
Nick Casagrande
09/24/2019, 11:51 AMNp. Keep in mind upm had no issues with v4 drivers. Only fsl did.
j
James Kindon
09/24/2019, 11:56 AMYup it's an fslogix gig 🤘
j
Julian Jakob
11/14/2019, 1:32 PM@Nick Casagrande could you please tell me what was your problem, again? Because of only 10.000 messages history, your original thread isn't visible. Thank you!
n
Nick Casagrande
11/14/2019, 1:43 PMentire thread is here - https://social.msdn.microsoft.com/Forums/en-US/home?forum=FSLogix