Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog

Deployment Solution 7.1 – Linux Known Issues/Limitations

Created: 18 Aug 2011 • Updated: 18 Aug 2011 • 5 comments
Sachin_Joshi5's picture
0 0 Votes
Login to vote

This blog lists different Linux known issues & limitations in Deployment Solution 7.1 and its components. The items in list will change as and when some support will come in the product or some new issue needs to be documented.
 

Following are the known issues/limitations in Deployment Solutions 7.1 pertaining to  Linux:

  1. Imaging of Dual boot(Linux & Window) disk is not supported by DS: Creating & restoring image of dual boot disk is not supported by Ghost & ultimately by DS 7.1.
  2. Creating Ext3/Ext4 partitions through DS is not supported: Ext3/Ext4 partition creation is not supported through DS. Only ext2 partitions  can be created using DS partitioning mechanism.
  3. Creating image on HTTP/HTTPS server with authentication is not supported: Creating image on HTTP/HTTPS with authentication is not supported. 
  4. Linux Scripted OS Install is not supported on IDE devices: Linux SOI is not supported on IDE disks.  
  5. Copy file task fails if password of task contains space: Copy file task fails in both Automation & Production of Linux if password of task contains space.
  6. Create image on http fails if image name contains space: In Create Image task, space in the image name is not supported when the image in being created on http location.
  7. SOI task fails if http source is on non-default port: Linux SOI task fails to execute if http source is on non-default port
  8. Concurrent SOI on multiple machine fails: Running Scripted OS install on multiple machine concurrently lists entry of only one machine under console.
  9. Ext4 is not supported yet by Ghost: Ext4 filesystem is not officially supported by ghost as imaging tool yet.
  10. RaiserFS is not supported yet by Ghost: If a client is configured with RaiserFS filesystem then capture of that filesystem is by sector-by-sector mode. Hence create image & deploy image will take more time compared to other know Linux filesystem such as ext2,ext3

Comments 5 CommentsJump to latest comment

Geek786's picture

Hi Sachin, 

Is the point number one still valid with the current release?

'Imaging of Dual boot(Linux & Window) disk is not supported by DS'

-1
Login to vote
epkpej's picture

Hi Sachin,

What is the current status of these Issues/Limitations? Which works in the current release of DS and which will work in the upcoming ITMS7.5 version?

+1
Login to vote
Sachin_Joshi5's picture

Hi Geek786,

Sorry for the delay.. I missed to answer this.

Yes. 'Imaging of Dual boot(Linux & Window) disk is not supported by DS'  stands true for DS 7.5(upcoming) and older releases.

Thanks,
Sachin

 

 

 

+1
Login to vote
Sachin_Joshi5's picture

 Hi epkpej,

Thanks. I will publish the up-to-date list for DS 7.5 ASAP.

Thanks,
Sachin

+5
Login to vote
Sachin_Joshi5's picture

 

Following are the known issues/limitations in Deployment Solutions 7.1 SP2 & 7.5(beta) pertaining to  Linux:

  1. Imaging of Dual boot(Linux & Window) disk is not supported by DS: Creating & restoring image of dual boot disk is not supported by Ghost & ultimately by DS.
  2. Creating Ext3/Ext4 partitions through DS is not supported: Ext3/Ext4 partition creation is not supported through DS. Only ext2 partitions  can be created using DS partitioning mechanism.
  3. Linux Scripted OS Install is not supported on IDE devices: Linux SOI is not supported on IDE disks.
  4. RaiserFS is not supported yet by Ghost: If a client is configured with RaiserFS filesystem then capture of that filesystem is by sector-by-sector mode. Hence create image & deploy image will take more time compared to other know Linux filesystem such as ext2,ext3,ext4
  5. Rdepoy - imaging tool, does not support RHEL6.x platforms
  6. ESX/ESXi 4.x SOI - Unlike Linux SOI, ESX/ESX 4.x SOI task will install only OS. ESX/ESX 4.x machine are not managed by DS.
  7. EXT4 as boot partition- If boot partition of a Linux client has ext4 as filesystem then boot to Automation won't work. In that case, user should use PXE to boot client.  If user is manually installing RHEL6.x that has ext4 as default filesystem hence keep boot partition as ext3 other partitions can be ext4 to use 'boot to automation' task.       
    Installing RHEL6.x using Linux SOI with default answer file provided by DS will set boot partition to ext3.

I will update this list if anything changes.

Thanks,
Sachin

 

+5
Login to vote