Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Channel Catalog


Channel Description:

Latest Message Board Threads at StudioSysAdmins

older | 1 | .... | 183 | 184 | (Page 185) | 186 | 187 | newer

    0 0

    You're invited: Shotgun BBQ, Beers and Bluegrass in Vancouver July 10
    posted by Kerry Corlett on July 6, 2018, 11:20 a.m. (3 days ago)

    Please join us for a Shotgun info-session with Christopher Sinnott, a member of the “Shotgun Rangers” team at Autodesk, followed by “BBQ, Beers and Bluegrass” on Tuesday, July 10 at Annex Pro. 

     

    Great food, craft beers, industry friends and live band Rollin’ Trainwreck! 

     

    Details and RSVP at https://autodesk-shotgun-bbq.eventbrite.com/?aff=SSA

     

    Thread Tags:
      discuss-at-studiosysadmins 

    0 Responses     0 Plus One's     0 Comments  
     

    Please join us for a Shotgun info-session with Christopher Sinnott, a member of the “Shotgun Rangers” team at Autodesk, followed by “BBQ, Beers and Bluegrass” on Tuesday, July 10 at Annex Pro. 

     

    Great food, craft beers, industry friends and live band Rollin’ Trainwreck! 

     

    Details and RSVP at https://autodesk-shotgun-bbq.eventbrite.com/?aff=SSA

     


    0 0

    StudioSysAdmins 10 Year Anniversary Studio Mingle
    posted by John Hickson on July 11, 2018, 8:33 a.m. (1 day ago)

    Please join us this year at SIGGRAPH for our 10 Year Anniversary!

     

    StudioSysAdmins 10 Year Anniversay StudioMingle

    Tuesday August 14th, 7pm-10pm at the Cypress Suite in the Pan Pacific Hotel.

    in beautiful Vancouver, British Columbia

     

    Event Link to see more details and out current sponsors

    http://www.studiosysadmins.com/events/view/225/

     

    We are still looking for more sponsors from Vendors and VARs, please contact me if you are interested in helping with this event. john.hickson@studiosysadmins.com

     

    Thread Tags:
      fun party SIGGRAPH event vancouver 

    0 Responses     0 Plus One's     0 Comments  
     

    Please join us this year at SIGGRAPH for our 10 Year Anniversary!

     

    StudioSysAdmins 10 Year Anniversay StudioMingle

    Tuesday August 14th, 7pm-10pm at the Cypress Suite in the Pan Pacific Hotel.

    in beautiful Vancouver, British Columbia

     

    Event Link to see more details and out current sponsors

    http://www.studiosysadmins.com/events/view/225/

     

    We are still looking for more sponsors from Vendors and VARs, please contact me if you are interested in helping with this event. john.hickson@studiosysadmins.com

     


    0 0

    Do you use Force 10 / Dell S3048-ON, S4048-ON, S4048T-ON, S6010-ON, S6100-ON, Z9100-ON or C9010 switches?
    posted by Greg Whynott on July 12, 2018, 5:50 p.m. (1 day ago)
    If you don't use these switches, bail now.


    You need to read this before rebooting them, if your switch has been up for greater than 18 months, it may not reboot again. The hardware clock may fail causing the CPU to lock up.





    I'm kind of disappointed with Dell right now, (imagine that, me being upset at a vendor!!). We have paid support on these switches for years, which has to be over 10k in support by now (cluster of them). This notice comes out which is as serious as it gets. Did our rep reach out to us and say "heads up!", no... Did Dell themselves send us a note saying "heads up", no.... but do they send us a note when we are almost due to give them more money for 'support'? Hell yes. Selective proactiveness.. :)



    Our have been up for over 2 years, trying to get one on site before we update and reboot.


    -greg





    Thread Tags:
      discuss-at-studiosysadmins 

    0 Responses     0 Plus One's     0 Comments  
     
    If you don't use these switches, bail now.


    You need to read this before rebooting them, if your switch has been up for greater than 18 months, it may not reboot again. The hardware clock may fail causing the CPU to lock up.





    I'm kind of disappointed with Dell right now, (imagine that, me being upset at a vendor!!). We have paid support on these switches for years, which has to be over 10k in support by now (cluster of them). This notice comes out which is as serious as it gets. Did our rep reach out to us and say "heads up!", no... Did Dell themselves send us a note saying "heads up", no.... but do they send us a note when we are almost due to give them more money for 'support'? Hell yes. Selective proactiveness.. :)



    Our have been up for over 2 years, trying to get one on site before we update and reboot.


    -greg






    0 0

    MPAA/Studio Internet VDI (or airgap)
    posted by MarcBrewster on July 16, 2018, 10:16 a.m.

    Hi All,

    Long time no hear.

     

    Just landed here at Union VFX and we have a VDI Internet solution for compliance purposes but I have to say that Im not massively impressed.

    http://lightpointsecurity.com/remote-browser-light-point-web

    Looking through the previous threads the last I could find was from 2016.

     

    Does anybody else have a system that they a) like, b) afford and c) reccomend??

     

    Cheers

    Marc


    0 Responses     0 Plus One's     1 Comments  
     

    Hi All,

    Long time no hear.

     

    Just landed here at Union VFX and we have a VDI Internet solution for compliance purposes but I have to say that Im not massively impressed.

    http://lightpointsecurity.com/remote-browser-light-point-web

    Looking through the previous threads the last I could find was from 2016.

     

    Does anybody else have a system that they a) like, b) afford and c) reccomend??

     

    Cheers

    Marc


    0 0
  • 07/20/18--12:15: AV signal noise debug
  • AV signal noise debug
    posted by Brian Krusic on July 20, 2018, 3:15 p.m. (3 days ago)
    Hi,

    Would any one happen to know some one in the Los Angeles area who can help me debug some signal noise?

    Dont ya just love some signal noise

    Thanks in advance,

    - Brian

    Every day is a gift
    Thats why they call it the present"

    Thread Tags:
      discuss-at-studiosysadmins 

    0 Responses     0 Plus One's     0 Comments  
     
    Hi,

    Would any one happen to know some one in the Los Angeles area who can help me debug some signal noise?

    Dont ya just love some signal noise

    Thanks in advance,

    - Brian

    Every day is a gift
    Thats why they call it the present"


    0 0
  • 07/20/18--22:02: Rendering Requirements
  • Rendering Requirements
    posted by Rick Grandy on July 21, 2018, 1:02 a.m. (2 days ago)

    Hey all,

    We are trying to collect some basic data about rendering from across the entire landscape, from small independent shops to large studio outfits.  Our goal is to better understand the requirements so we can create products that would work well for your use cases.  If you can provide this type of feedback, it would be great to hear from you.  This is what we are looking for:

     

    How many farm jobs/tasks did you render last month/3 months/ 6 months/ year?

    For each job:

        Total time from start to finish

        Number of frames

        Average time per frame

        Size of job frame on disk  (assets not output)

        Size of job frame in memory (working rendering set)

        Resolution of frames

     

    What is the configuration of your render nodes:

        # of CPUs

        # of physical cores per CPU

        Clock speed

        Do you use hyperthreading

        amount  of RAM in node

        network interface type

        local storage

        # of GPUs

        model of GPUs

     

     

    Do you try maintain certain scene size limits?

        If yes, what is the limit?

        What is the trade-off?

     

    What do you see as the average heavy and light scenes to render? (time, memory usage, etc)

     

    You help is very much appreciated.

    Regards,

    Rick

     

    Thread Tags:
      rendering memory cpu gpu renderer 

    0 Responses     0 Plus One's     0 Comments  
     

    Hey all,

    We are trying to collect some basic data about rendering from across the entire landscape, from small independent shops to large studio outfits.  Our goal is to better understand the requirements so we can create products that would work well for your use cases.  If you can provide this type of feedback, it would be great to hear from you.  This is what we are looking for:

     

    How many farm jobs/tasks did you render last month/3 months/ 6 months/ year?

    For each job:

        Total time from start to finish

        Number of frames

        Average time per frame

        Size of job frame on disk  (assets not output)

        Size of job frame in memory (working rendering set)

        Resolution of frames

     

    What is the configuration of your render nodes:

        # of CPUs

        # of physical cores per CPU

        Clock speed

        Do you use hyperthreading

        amount  of RAM in node

        network interface type

        local storage

        # of GPUs

        model of GPUs

     

     

    Do you try maintain certain scene size limits?

        If yes, what is the limit?

        What is the trade-off?

     

    What do you see as the average heavy and light scenes to render? (time, memory usage, etc)

     

    You help is very much appreciated.

    Regards,

    Rick

     


    0 0

    join linux machines to domain without password prompt.
    posted by Greg Whynott on July 23, 2018, 1 p.m.
    If you don't join linux machines to AD bail now,



    Should it be helpful...


    During my move from NSLCD to SSSD one of the challenges was adding machines to the domain silently without interaction required.

    Both the realm and net command require you to enter your password and neither (from what I can tell) have a flag to pass the password along on the command line.

    There are many articles on how to do this as a one off, typically requiring you to pre-add the machine to the domain, one time pass or similar. These methods don't scale well beyond 1 machine.

    My intention was to deploy hundreds of machines using kickstart and have them all 100% done when the installer finished up, unattended.

    After a lot of searching for methods and without much luck, unix itself provided the method. Should of been obvious but I guess my head was in windows mode at the time.

    if you type:

    realm join ad01.mydomain.com -U accountname

    It'll ask you for a password. To get around this, instead type:

    echo mypassword | realm join ad01.mydomain.com -U accountname


    power of the pipe!


    kinit works the same:

    echo mypassword | kinit -U accountname


    greg





    Thread Tags:
      discuss-at-studiosysadmins 

    0 Responses     0 Plus One's     0 Comments  
     
    If you don't join linux machines to AD bail now,



    Should it be helpful...


    During my move from NSLCD to SSSD one of the challenges was adding machines to the domain silently without interaction required.

    Both the realm and net command require you to enter your password and neither (from what I can tell) have a flag to pass the password along on the command line.

    There are many articles on how to do this as a one off, typically requiring you to pre-add the machine to the domain, one time pass or similar. These methods don't scale well beyond 1 machine.

    My intention was to deploy hundreds of machines using kickstart and have them all 100% done when the installer finished up, unattended.

    After a lot of searching for methods and without much luck, unix itself provided the method. Should of been obvious but I guess my head was in windows mode at the time.

    if you type:

    realm join ad01.mydomain.com -U accountname

    It'll ask you for a password. To get around this, instead type:

    echo mypassword | realm join ad01.mydomain.com -U accountname


    power of the pipe!


    kinit works the same:

    echo mypassword | kinit -U accountname


    greg






    0 0

    join linux machines to domain without password prompt.
    posted by Rory Falloon on July 23, 2018, 1:05 p.m.


    net ads join -Uusername%password also works.


    From: studiosysadmins-discuss-bounces@studiosysadmins.com <studiosysadmins-discuss-bounces@studiosysadmins.com> on behalf of greg whynott <greg.whynott@gmail.com>
    Sent: Monday, July 23, 2018 12:58 PM
    To: studiosysadmins-discuss
    Subject: [SSA-Discuss] join linux machines to domain without password prompt.
     
    If you don't join linux machines to AD bail now,



    Should it be helpful...


    During my move from NSLCD to SSSD one of the challenges was adding machines to the domain silently without interaction required.

    Both the realm and net command require you to enter your password and neither (from what I can tell) have a flag to pass the password along on the command line.  

    There are many articles on how to do this as a one off,  typically requiring you to pre-add the machine to the domain, one time pass or similar.  These methods don't scale well beyond 1 machine.

    My intention was to deploy hundreds of machines using kickstart and have them all 100% done when the installer finished up,  unattended. 

    After a lot of searching for methods and without much luck,  unix itself provided the method.  Should of been obvious but I guess my head was in windows mode at the time.

    if you type:

    realm join ad01.mydomain.com -U accountname

    It'll ask you for a password.  To get around this,  instead type:

    echo mypassword | realm join ad01.mydomain.com -U accountname


    power of the pipe!


    kinit works the same:

    echo mypassword | kinit -U accountname


    greg





    Thread Tags:
      discuss-at-studiosysadmins 

    0 Responses     0 Plus One's     0 Comments  
     


    net ads join -Uusername%password also works.


    From: studiosysadmins-discuss-bounces@studiosysadmins.com <studiosysadmins-discuss-bounces@studiosysadmins.com> on behalf of greg whynott <greg.whynott@gmail.com>
    Sent: Monday, July 23, 2018 12:58 PM
    To: studiosysadmins-discuss
    Subject: [SSA-Discuss] join linux machines to domain without password prompt.
     
    If you don't join linux machines to AD bail now,



    Should it be helpful...


    During my move from NSLCD to SSSD one of the challenges was adding machines to the domain silently without interaction required.

    Both the realm and net command require you to enter your password and neither (from what I can tell) have a flag to pass the password along on the command line.  

    There are many articles on how to do this as a one off,  typically requiring you to pre-add the machine to the domain, one time pass or similar.  These methods don't scale well beyond 1 machine.

    My intention was to deploy hundreds of machines using kickstart and have them all 100% done when the installer finished up,  unattended. 

    After a lot of searching for methods and without much luck,  unix itself provided the method.  Should of been obvious but I guess my head was in windows mode at the time.

    if you type:

    realm join ad01.mydomain.com -U accountname

    It'll ask you for a password.  To get around this,  instead type:

    echo mypassword | realm join ad01.mydomain.com -U accountname


    power of the pipe!


    kinit works the same:

    echo mypassword | kinit -U accountname


    greg






    0 0

    join linux machines to domain without password prompt.
    posted by Greg Whynott on July 23, 2018, 2 p.m. (1 day ago)
    Thanks Rory, we are not using net to join machines but good to know.

    -g



    On Mon, Jul 23, 2018 at 1:00 PM, Rory Falloon <rory@mrxfx.com> wrote:


    net ads join -Uusername%password also works.


    From:studiosysadmins-discuss-bounces@studiosysadmins.com<studiosysadmins-discuss-bounces@studiosysadmins.com> on behalf of greg whynott <greg.whynott@gmail.com>
    Sent: Monday, July 23, 2018 12:58 PM
    To: studiosysadmins-discuss
    Subject: [SSA-Discuss] join linux machines to domain without password prompt.
    If you don't join linux machines to AD bail now,



    Should it be helpful...


    During my move from NSLCD to SSSD one of the challenges was adding machines to the domain silently without interaction required.

    Both the realm and net command require you to enter your password and neither (from what I can tell) have a flag to pass the password along on the command line.

    There are many articles on how to do this as a one off, typically requiring you to pre-add the machine to the domain, one time pass or similar. These methods don't scale well beyond 1 machine.

    My intention was to deploy hundreds of machines using kickstart and have them all 100% done when the installer finished up, unattended.

    After a lot of searching for methods and without much luck, unix itself provided the method. Should of been obvious but I guess my head was in windows mode at the time.

    if you type:

    realm join ad01.mydomain.com -U accountname

    It'll ask you for a password. To get around this, instead type:

    echo mypassword | realm join ad01.mydomain.com -U accountname


    power of the pipe!


    kinit works the same:

    echo mypassword | kinit -U accountname


    greg






    To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe

    Thread Tags:
      discuss-at-studiosysadmins 

    0 Responses     0 Plus One's     0 Comments  
     
    Thanks Rory, we are not using net to join machines but good to know.

    -g



    On Mon, Jul 23, 2018 at 1:00 PM, Rory Falloon <rory@mrxfx.com> wrote:


    net ads join -Uusername%password also works.


    From:studiosysadmins-discuss-bounces@studiosysadmins.com<studiosysadmins-discuss-bounces@studiosysadmins.com> on behalf of greg whynott <greg.whynott@gmail.com>
    Sent: Monday, July 23, 2018 12:58 PM
    To: studiosysadmins-discuss
    Subject: [SSA-Discuss] join linux machines to domain without password prompt.
    If you don't join linux machines to AD bail now,



    Should it be helpful...


    During my move from NSLCD to SSSD one of the challenges was adding machines to the domain silently without interaction required.

    Both the realm and net command require you to enter your password and neither (from what I can tell) have a flag to pass the password along on the command line.

    There are many articles on how to do this as a one off, typically requiring you to pre-add the machine to the domain, one time pass or similar. These methods don't scale well beyond 1 machine.

    My intention was to deploy hundreds of machines using kickstart and have them all 100% done when the installer finished up, unattended.

    After a lot of searching for methods and without much luck, unix itself provided the method. Should of been obvious but I guess my head was in windows mode at the time.

    if you type:

    realm join ad01.mydomain.com -U accountname

    It'll ask you for a password. To get around this, instead type:

    echo mypassword | realm join ad01.mydomain.com -U accountname


    power of the pipe!


    kinit works the same:

    echo mypassword | kinit -U accountname


    greg






    To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe


    0 0

    join linux machines to domain without password prompt.
    posted by Rory Falloon on July 23, 2018, 2:05 p.m. (1 day ago)
    This begs the question (which I should know the answers to) but what are the differences in the various ways to join a domain? 

    Sent from my iPhone with a soon to be cracked or broken screen.

    On Jul 23, 2018, at 13:59, greg whynott <greg.whynott@gmail.com> wrote:

    Thanks Rory,  we are not using net to join machines but good to know.   

    -g



    On Mon, Jul 23, 2018 at 1:00 PM, Rory Falloon <rory@mrxfx.com> wrote:


    net ads join -Uusername%password also works.


    From: studiosysadmins-discuss-bounces@studiosysadmins.com<studiosysadmins-discuss-bounces@studiosysadmins.com> on behalf of greg whynott <greg.whynott@gmail.com>
    Sent: Monday, July 23, 2018 12:58 PM
    To: studiosysadmins-discuss
    Subject: [SSA-Discuss] join linux machines to domain without password prompt.
     
    If you don't join linux machines to AD bail now,



    Should it be helpful...


    During my move from NSLCD to SSSD one of the challenges was adding machines to the domain silently without interaction required.

    Both the realm and net command require you to enter your password and neither (from what I can tell) have a flag to pass the password along on the command line.  

    There are many articles on how to do this as a one off,  typically requiring you to pre-add the machine to the domain, one time pass or similar.  These methods don't scale well beyond 1 machine.

    My intention was to deploy hundreds of machines using kickstart and have them all 100% done when the installer finished up,  unattended. 

    After a lot of searching for methods and without much luck,  unix itself provided the method.  Should of been obvious but I guess my head was in windows mode at the time.

    if you type:

    realm join ad01.mydomain.com -U accountname

    It'll ask you for a password.  To get around this,  instead type:

    echo mypassword | realm join ad01.mydomain.com -U accountname


    power of the pipe!


    kinit works the same:

    echo mypassword | kinit -U accountname


    greg






    To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe

    Thread Tags:
      discuss-at-studiosysadmins 

    0 Responses     0 Plus One's     0 Comments  
     
    This begs the question (which I should know the answers to) but what are the differences in the various ways to join a domain? 

    Sent from my iPhone with a soon to be cracked or broken screen.

    On Jul 23, 2018, at 13:59, greg whynott <greg.whynott@gmail.com> wrote:

    Thanks Rory,  we are not using net to join machines but good to know.   

    -g



    On Mon, Jul 23, 2018 at 1:00 PM, Rory Falloon <rory@mrxfx.com> wrote:


    net ads join -Uusername%password also works.


    From: studiosysadmins-discuss-bounces@studiosysadmins.com<studiosysadmins-discuss-bounces@studiosysadmins.com> on behalf of greg whynott <greg.whynott@gmail.com>
    Sent: Monday, July 23, 2018 12:58 PM
    To: studiosysadmins-discuss
    Subject: [SSA-Discuss] join linux machines to domain without password prompt.
     
    If you don't join linux machines to AD bail now,



    Should it be helpful...


    During my move from NSLCD to SSSD one of the challenges was adding machines to the domain silently without interaction required.

    Both the realm and net command require you to enter your password and neither (from what I can tell) have a flag to pass the password along on the command line.  

    There are many articles on how to do this as a one off,  typically requiring you to pre-add the machine to the domain, one time pass or similar.  These methods don't scale well beyond 1 machine.

    My intention was to deploy hundreds of machines using kickstart and have them all 100% done when the installer finished up,  unattended. 

    After a lot of searching for methods and without much luck,  unix itself provided the method.  Should of been obvious but I guess my head was in windows mode at the time.

    if you type:

    realm join ad01.mydomain.com -U accountname

    It'll ask you for a password.  To get around this,  instead type:

    echo mypassword | realm join ad01.mydomain.com -U accountname


    power of the pipe!


    kinit works the same:

    echo mypassword | kinit -U accountname


    greg






    To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe


    0 0

    Deadline Render Queue software
    posted by brad falk on July 23, 2018, 10:31 p.m. (1 day ago)

    Sorry to start yet another thread. But I have a question about Thinkbox Deadline.

    I wanted to find out if there is a way to have a deadline slave rejoin the render queue after a reboot automatically even if the slave does not have a user logged in. We just changed from windows workgroup to Domain Server. All machines used to automatically login as admin when rebooted but now requires manual login. Does anyone know how to get around this?

    Thank you

    Brad Falk

     

    Thread Tags:
      slave 

    0 Responses     1 Plus One's     0 Comments  
     

    Sorry to start yet another thread. But I have a question about Thinkbox Deadline.

    I wanted to find out if there is a way to have a deadline slave rejoin the render queue after a reboot automatically even if the slave does not have a user logged in. We just changed from windows workgroup to Domain Server. All machines used to automatically login as admin when rebooted but now requires manual login. Does anyone know how to get around this?

    Thank you

    Brad Falk

     


    0 0
  • 07/25/18--02:40: netflix snowball
  • netflix snowball
    posted by Julian Firminger on July 25, 2018, 5:40 a.m.
    Fellow music lovers,

    Is anyone out there a Netflix TPN who is successfully using Snowball Edge? We're trialing one now and are having all sorts of problems getting it to talk turkey.

    I'm wondering if Snowball is new to Netflix..

    Anyone get it working / use it in production? I'd love a chat offline if you are. (or Slack PM)

    Cheers,

    Julian Firminger

    Senior Systems Administrator
    United Broadcast Facilities
    Amsterdam, The Netherlands
    Thread Tags:
      discuss-at-studiosysadmins 

    0 Responses     0 Plus One's     0 Comments  
     
    Fellow music lovers,

    Is anyone out there a Netflix TPN who is successfully using Snowball Edge? We're trialing one now and are having all sorts of problems getting it to talk turkey.

    I'm wondering if Snowball is new to Netflix..

    Anyone get it working / use it in production? I'd love a chat offline if you are. (or Slack PM)

    Cheers,

    Julian Firminger

    Senior Systems Administrator
    United Broadcast Facilities
    Amsterdam, The Netherlands

    0 0

    Meraki. Why I'll never use them again.
    posted by Greg Whynott on July 26, 2018, 12:25 p.m.
    If you are not in the market for a firewall, APs or switch bail now. If you are and considering Meraki, might want to read the below and do some googling. Its a bit long, sorry...



    Back many moons ago I posted about a Meraki device I acquired. At first I was impressed with them, but that was before I started actually using them in a production environment.


    Fast forward 2 or 3 years of using them and I am now of the opinion they are a steaming pile of _____. The hardware itself may be ok but everything beyond that has been a horrible experience.


    For a small shop without the resources or skill set, I could see why someone might want to consider them. Even in that situation I would highly encourage someone to look elsewhere, such as Ubiquiti Network's offerings, which I have deployed for some side contract clients and they have been problem free and happy ever since.


    I could go on at length about the things I perceive as problem areas with them but the items below is why I'll never deal with them again. Buyt me a beer and I'll entertain you more. ;)


    1. Licensing. This model is setup to extort, blackmail and be as clear as mud to the customer. Look at this and tell me how it makes sense. Its almost amusing listening to them try and explain it as if it was perfectly legit.

    - we bought an MX100 for our VPN requirements. 1 year license
    - acquired a MX65 with 3 year license for the wifi fw.

    For about a year these were under the same 'network' on their dashboard. I went to apply another year license to the MX100 when it still had 40 days of support left on it according the dashboard. When I applied the license it said it would expire in about 7 months. Scratching my head, I give them a call. In my mind we have over a year left on the MX65 and I just added another year of support to the MX100, why less than a year?

    After talking to them and listening at length about 'co termination' BS and how they are shared, which still didn't add up in my mind, I asked "if we spit them so they are not sharing licenses, will this fix things?" The answer was similar to "yes, then each license will reflect the full amount"..


    So I split the networks.. After that was done I applied the 1 year license, in my mind with about 30 days remaining on the support for the MX100, adding a MX100 1 year support license should give me about 390 days of support. Instead it was 309 days!!! WTF, how does that work?

    Then I look at my MX64 dashboard and see it says it'll expire NEXT month! Wait, we should still have about a year on that one....


    So I ask "whats up here, please explain"...

    The answer I get back is they are "sharing their time". The optics suggest they straight up ripped us off for about 2 years of support.

    I'm still working with them on this in an effort to understand or correct, maybe common sense will prevail but confidence is low. I've never seen a more cantankerous licensing model in my life. Talk about smoke and mirrors and making it as complex as possible. The internet is full of people complaining about this, for a while I thought I was the only one who didn't "get it"...

    How does applying a new 1 year license end up extending it by only 309 days on the MX100 and makes the MX65 expire what appears to be 11 months prematurely? So odd...

    One guy got a free "life time license" but after he started using it and added more Meraki devices, his life time license morphed into a 3 year license and Merakie's answer to that was "that makes sense"... ( https://community.spiceworks.com/topic/1425017-meraki-licensing-not-so-nice )


    2. No insight. I have opened about 20 tickets over the last 2 years for things I could of easily looked into myself. But because they offer no access to the device, you can't view debug logs or any other problem solving / investigation yourself without involving them.


    3. Support. its a bunch of kids it appears. I noticed the Meraki was literately scanning our internal networks. Every day we would get 100's of messages that the MX100 was connecting to port 7 on all our internal machines. I open a ticket and the answer I get back after several weeks of back and forth (at one point support said "that's not port 7, that's the window size of the packet") A network support team who doesn't understand basic networking or able to decode a simple packet trace.. great. They claim the Meraki is connecting to my internal machines because we are using AD to authenticate.. ???? ok....

    Then they ask me "I see the account ads_proxy is used by a lot of machines, can you tell us about that account?". ads_proxy is the account we use to bind to the AD. How do they know all our internal machines are using that account to bind to the AD? This is a VPN device, there are no default routes to it. It concerns me they have such insight to our internal network. Were they doing unauthorized queries to our AD of some sort? It seems dirty and bad. I can't even add a rule to prevent this.


    tldr. :)


    -g
























    Thread Tags:
      discuss-at-studiosysadmins 

    0 Responses     0 Plus One's     0 Comments  
     
    If you are not in the market for a firewall, APs or switch bail now. If you are and considering Meraki, might want to read the below and do some googling. Its a bit long, sorry...



    Back many moons ago I posted about a Meraki device I acquired. At first I was impressed with them, but that was before I started actually using them in a production environment.


    Fast forward 2 or 3 years of using them and I am now of the opinion they are a steaming pile of _____. The hardware itself may be ok but everything beyond that has been a horrible experience.


    For a small shop without the resources or skill set, I could see why someone might want to consider them. Even in that situation I would highly encourage someone to look elsewhere, such as Ubiquiti Network's offerings, which I have deployed for some side contract clients and they have been problem free and happy ever since.


    I could go on at length about the things I perceive as problem areas with them but the items below is why I'll never deal with them again. Buyt me a beer and I'll entertain you more. ;)


    1. Licensing. This model is setup to extort, blackmail and be as clear as mud to the customer. Look at this and tell me how it makes sense. Its almost amusing listening to them try and explain it as if it was perfectly legit.

    - we bought an MX100 for our VPN requirements. 1 year license
    - acquired a MX65 with 3 year license for the wifi fw.

    For about a year these were under the same 'network' on their dashboard. I went to apply another year license to the MX100 when it still had 40 days of support left on it according the dashboard. When I applied the license it said it would expire in about 7 months. Scratching my head, I give them a call. In my mind we have over a year left on the MX65 and I just added another year of support to the MX100, why less than a year?

    After talking to them and listening at length about 'co termination' BS and how they are shared, which still didn't add up in my mind, I asked "if we spit them so they are not sharing licenses, will this fix things?" The answer was similar to "yes, then each license will reflect the full amount"..


    So I split the networks.. After that was done I applied the 1 year license, in my mind with about 30 days remaining on the support for the MX100, adding a MX100 1 year support license should give me about 390 days of support. Instead it was 309 days!!! WTF, how does that work?

    Then I look at my MX64 dashboard and see it says it'll expire NEXT month! Wait, we should still have about a year on that one....


    So I ask "whats up here, please explain"...

    The answer I get back is they are "sharing their time". The optics suggest they straight up ripped us off for about 2 years of support.

    I'm still working with them on this in an effort to understand or correct, maybe common sense will prevail but confidence is low. I've never seen a more cantankerous licensing model in my life. Talk about smoke and mirrors and making it as complex as possible. The internet is full of people complaining about this, for a while I thought I was the only one who didn't "get it"...

    How does applying a new 1 year license end up extending it by only 309 days on the MX100 and makes the MX65 expire what appears to be 11 months prematurely? So odd...

    One guy got a free "life time license" but after he started using it and added more Meraki devices, his life time license morphed into a 3 year license and Merakie's answer to that was "that makes sense"... ( https://community.spiceworks.com/topic/1425017-meraki-licensing-not-so-nice )


    2. No insight. I have opened about 20 tickets over the last 2 years for things I could of easily looked into myself. But because they offer no access to the device, you can't view debug logs or any other problem solving / investigation yourself without involving them.


    3. Support. its a bunch of kids it appears. I noticed the Meraki was literately scanning our internal networks. Every day we would get 100's of messages that the MX100 was connecting to port 7 on all our internal machines. I open a ticket and the answer I get back after several weeks of back and forth (at one point support said "that's not port 7, that's the window size of the packet") A network support team who doesn't understand basic networking or able to decode a simple packet trace.. great. They claim the Meraki is connecting to my internal machines because we are using AD to authenticate.. ???? ok....

    Then they ask me "I see the account ads_proxy is used by a lot of machines, can you tell us about that account?". ads_proxy is the account we use to bind to the AD. How do they know all our internal machines are using that account to bind to the AD? This is a VPN device, there are no default routes to it. It concerns me they have such insight to our internal network. Were they doing unauthorized queries to our AD of some sort? It seems dirty and bad. I can't even add a rule to prevent this.


    tldr. :)


    -g

























    0 0
  • 07/26/18--10:45: Baselight hardware?
  • Baselight hardware?
    posted by Rob LaRose on July 26, 2018, 1:45 p.m.

    Is anybody using Baselight? We're looking at it and wondering about hardware/slots/etc restrictions.

    --Rob



    --
    Rob LaRose
    engineer |rock paper scissors
    245 5th ave 23rd floor new york ny 10016| O212 255 6446


    Thread Tags:
      discuss-at-studiosysadmins 

    0 Responses     0 Plus One's     0 Comments  
     

    Is anybody using Baselight? We're looking at it and wondering about hardware/slots/etc restrictions.

    --Rob



    --
    Rob LaRose
    engineer |rock paper scissors
    245 5th ave 23rd floor new york ny 10016| O212 255 6446



    0 0
  • 07/26/18--10:50: Method bought Atomic
  • Method bought Atomic
    posted by Shawn Wallbridge on July 26, 2018, 1:50 p.m.
    http://www.atomicfiction.com/method Crazyness shawn To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe
    Thread Tags:
      discuss-at-studiosysadmins 

    0 Responses     0 Plus One's     0 Comments  
     
    http://www.atomicfiction.com/method Crazyness shawn To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe

    0 0
  • 07/26/18--12:40: Sys Admin Day July 27
  • Sys Admin Day July 27
    posted by Brian Krusic on July 26, 2018, 3:40 p.m.
    Hi,

    Just wanted every one to be ready ahead of time.

    Remember to have your Jack and Coke etc.. prepped and ready.

    - Brian

    Every day is a gift
    Thats why they call it the present"

    Thread Tags:
      discuss-at-studiosysadmins 

    0 Responses     0 Plus One's     0 Comments  
     
    Hi,

    Just wanted every one to be ready ahead of time.

    Remember to have your Jack and Coke etc.. prepped and ready.

    - Brian

    Every day is a gift
    Thats why they call it the present"


    0 0
  • 07/30/18--06:52: Siggraph pass
  • Siggraph pass
    posted by Sean Macrae on July 30, 2018, 9:52 a.m. (3 days ago)

    If anyone has a pass please let me know...we're on a slim budget ;)

     

    Thread Tags:
      siggraph 

    0 Responses     0 Plus One's     2 Comments  
     

    If anyone has a pass please let me know...we're on a slim budget ;)

     


    0 0

    PLUG: Cloud Rendering BoF at Siggraph: Mon 13 Aug 3-4pm
    posted by Bjorn Leffler on Aug. 7, 2018, 12:39 a.m.

    Please join us for a discussion about cloud rendering in the East Building, Room 11, Vancouver Convention Centre.

     
    Conveniently timed before the "Renderfarming" BoF at 4:30pm - 5:30pm, as well as the "Global VFX Pipeline" BoF at 5-7pm.

    Abstract:
    General discussion of cloud-based rendering: problems, solutions and best practices. Technical details related to networking, storage, performance, etc. Discussions around other cloud workloads are most welcome, eg. simulations and transcoding.

    Happy Siggraph!
    Bjorn
     
    Thread Tags:
      siggraph 

    0 Responses     0 Plus One's     0 Comments  
     

    Please join us for a discussion about cloud rendering in the East Building, Room 11, Vancouver Convention Centre.

     
    Conveniently timed before the "Renderfarming" BoF at 4:30pm - 5:30pm, as well as the "Global VFX Pipeline" BoF at 5-7pm.

    Abstract:
    General discussion of cloud-based rendering: problems, solutions and best practices. Technical details related to networking, storage, performance, etc. Discussions around other cloud workloads are most welcome, eg. simulations and transcoding.

    Happy Siggraph!
    Bjorn
     

    0 0

    PLUG: Cloud Rendering BoF at Siggraph: Mon 13 Aug 3-4pm
    posted by Chris Banal on Aug. 7, 2018, 7:10 p.m. (1 day ago)
    Sounds interesting. Is it on Monday or Tuesday? The siggraph website says Tuesday and thread title says Monday.


    Cloud Rendering
    G&IP&A
    Tuesday, 14 August 2018 3pm - 4pm East Building, Room 11, Vancouver Convention Centre
    General discussion of cloud-based rendering: problems, solutions and best practices. Technical details related to networking, storage, performance, etc. Discussions around other cloud workloads are most welcome, eg. simulations and transcoding.
    Bjorn LefflerGoogle

    On Mon, Aug 6, 2018 at 9:39 PM Bjorn Leffler <content@studiosysadmins.com> wrote:

    Please join us for a discussion about cloud rendering in the East Building, Room 11, Vancouver Convention Centre.

    Conveniently timed before the "Renderfarming" BoF at 4:30pm - 5:30pm, as well as the "Global VFX Pipeline" BoF at 5-7pm.

    Abstract:
    General discussion of cloud-based rendering: problems, solutions and best practices. Technical details related to networking, storage, performance, etc. Discussions around other cloud workloads are most welcome, eg. simulations and transcoding.

    Happy Siggraph!
    Bjorn
    To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe
    Thread Tags:
      discuss-at-studiosysadmins 

    0 Responses     0 Plus One's     0 Comments  
     
    Sounds interesting. Is it on Monday or Tuesday? The siggraph website says Tuesday and thread title says Monday.


    Cloud Rendering
    G&IP&A
    Tuesday, 14 August 2018 3pm - 4pm East Building, Room 11, Vancouver Convention Centre
    General discussion of cloud-based rendering: problems, solutions and best practices. Technical details related to networking, storage, performance, etc. Discussions around other cloud workloads are most welcome, eg. simulations and transcoding.
    Bjorn LefflerGoogle

    On Mon, Aug 6, 2018 at 9:39 PM Bjorn Leffler <content@studiosysadmins.com> wrote:

    Please join us for a discussion about cloud rendering in the East Building, Room 11, Vancouver Convention Centre.

    Conveniently timed before the "Renderfarming" BoF at 4:30pm - 5:30pm, as well as the "Global VFX Pipeline" BoF at 5-7pm.

    Abstract:
    General discussion of cloud-based rendering: problems, solutions and best practices. Technical details related to networking, storage, performance, etc. Discussions around other cloud workloads are most welcome, eg. simulations and transcoding.

    Happy Siggraph!
    Bjorn
    To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe

    0 0

    Invitation to SIGGRAPH Mixer w/Powerland
    posted by John Hickson on Aug. 9, 2018, 2:10 p.m. (2 days ago)

    Hey everyone,

    If you are attending SIGGRAPH and free on Monday evening...

    Date/Time : August 13, 2018 from 6:30pm - late

    Place: The Butcher & Bullock (911 W Pender St)

     

    RSVP: https://events.r20.constantcontact.com/register/eventReg?oeidk=a07efl39huna853d42e&oseq=&c=&ch=

     

     
    Thread Tags:
      discuss-at-studiosysadmins 

    0 Responses     0 Plus One's     0 Comments  
     

    Hey everyone,

    If you are attending SIGGRAPH and free on Monday evening...

    Date/Time : August 13, 2018 from 6:30pm - late

    Place: The Butcher & Bullock (911 W Pender St)

     

    RSVP: https://events.r20.constantcontact.com/register/eventReg?oeidk=a07efl39huna853d42e&oseq=&c=&ch=

     

     

older | 1 | .... | 183 | 184 | (Page 185) | 186 | 187 | newer