|
[Sponsors] |
Arguments for taking CFD Nodes out of Company Domain |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
April 30, 2015, 11:47 |
Arguments for taking CFD Nodes out of Company Domain
|
#1 |
New Member
Join Date: Mar 2009
Posts: 23
Rep Power: 17 |
Hi All,
Large Companies may ( or may not ) use Workstations (Nodes),that are on their Company Domain, for CFD analysis. The Nodes on Company Domain obey the IT Company Policy which normally requires: 1. Automatic downloading and installation of System Updates (most often the installation requires automatic reboot). 2. Scheduled maintenance procedures such as virus scan and disk defragmentation. All those interfere the CFD runs. In addition: 3. Companies with more than one Office could share their CFD resources across the Offices and that will require shared CFD Account - not allowed by the IT Policy on Company Domain. 4. CFD job may require Linux installation that is not supported on the Company Domain. What other arguments or issues do you experience when using a Company Domain Nodes for CFD job? - What else you could share in support that CFD hardware resources should be on separate CFD Domain that have a separate Server that hold all the licenses of Application Software related to the CFD Job. Thank you very much in advance for your input |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Domain Imbalance | HMR | CFX | 5 | October 10, 2016 05:57 |
injection problem | Mark New | FLUENT | 0 | August 4, 2013 01:30 |
Error finding variable "THERMX" | sunilpatil | CFX | 8 | April 26, 2013 07:00 |
CFX domain comparison | Kiat110616 | CFX | 4 | April 3, 2011 22:43 |
public CFD Code development | Heinz Wilkening | Main CFD Forum | 38 | March 5, 1999 11:44 |