Increase max file size limit cap on Synology Cloud Sync / Amazon Cloud Drive from 10 to 50Gb

EDIT :  Since release Version: 2.2.1-0858 , Added support for syncing files up to 45 GBs with ACD. This shim is no longer needed, unless you want to try higher

https://www.synology.com/en-us/releaseNote/CloudSync

 

 

I am the happy owner of an unlimited Amazon Cloud Drive unlimited subscription, by default the cap size is 10GB for syncing files to ACD via Synology’s Cloud Sync app.

But when you want to backup big .vhdx files or  big ISOs or whatever, you easily end up being bothered by the cap .

Warning : Do this modification at your own risk, vi editing system files can be dangerous. I will not be held responsible if anything goes wrong or you break something.

Here is an easy way :

  1. Stop Cloud Sync
  2. Launch a terminal session and run : sudo vi /var/packages/CloudSync/target/etc/clouddrive.filter
  3. Modify the max_size from 10GB to 50GB   (53687091200)
  4. Save and Quit
  5. Start Cloud Sync.
  6. Done!

Note , you should end up with a file like this:

[Version]
major = 1
minor = 1

[Common]
black_char = “:*?\”<>|\\/”
black_name = “@eaDir”, “.SynologyWorkingDirectory”, “#recycle”, “desktop.ini”, “.ds_store”, “Icon\r”, “thumbs.db”, “$Recycle.Bin”, “@sharebin”, “@SynologyCloudSync”, “cloudsync_encrypt.info”, “#snapshot”
max_length = 255
max_path = 2048
max_server_path = 2048

[File]
black_name = “@eaDir”, “.SynologyWorkingDirectory”, “#recycle”, “desktop.ini”, “.ds_store”, “Icon\r”, “thumbs.db”, “$Recycle.Bin”, “@sharebin”, “@SynologyCloudSync”, “cloudsync_encrypt.info”, “#snapshot”
black_prefix = “._”, “~”, “.SYNOPPSDB”
max_size = 53687091200

[Directory]
black_name = “@eaDir”, “.SynologyWorkingDirectory”, “#recycle”, “desktop.ini”, “.ds_store”, “Icon\r”, “thumbs.db”, “$Recycle.Bin”, “@sharebin”, “@SynologyCloudSync”, “cloudsync_encrypt.info”, “#snapshot”

[EA]

 

Credits to Arthur REMY for the help:

http://arthurremy.com/

 

 

Add remote connection feature to WinPE during MDT/SCCM OSD

 

This method is fine if someone is at the other end to offer this information, but what if you want to remotely control a machine in WinPE without this hassle? Here is How:
End Goal: At the end of this guide, your boot images will automatically generate a shortcut file to allow users to easily remote control every machine that boots from your SCCM Boot wim, you will have a folder set up like this which will generate shortcut files to DART remote control, at the end of your build process it will be deleted :
Firstly, you will want to integrate Dart into your boot image:
(I’m assuming you are using SCCM/MDT Integration, you can make it work fine without, just google)
  1. Install DaRT 8.1 or 10 onto a workstation.
  2. Using File Explorer, navigate to the C:\Program Files\Microsoft DaRT\Version folder.a
  3. Copy the Toolsx86.cab file to C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Tools\x86
  4. Copy the Toolsx64.cab file to C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Tools\x64
  5. Create a new ConfigMgr Boot image using the MDT wizard; select the DaRT component during creation.
  6. For more info see here: http://deploymentresearch.com/Research/Post/334/Adding-DaRT-8-1-from-MDOP-2013-R2-to-ConfigMgr-2012-R2
Take your new boot image and mount it:
DISM.exe /Mount-Wim /WimFile:”C:\Users\admin\Desktop\winpe.wim” /index:1 /MountDir:”C:\Users\admin\Desktop\offline”
Go here to download the scripts and files you will need:  Files
From the downloaded files, please the following items in each location:
Place:
WinPE_DarT.ps1 >  \offline\Windows\System32
Unattend.xml >  \offline\Windows\System32
shortcutmap.txt > \offline\Windows\System32
DartConfig.dat >  \offline\Windows\System32
RemoveDartShortcut.ps1 > Into your OSD Script folder
WinPE_Dart.ps1 (Powershell script that does the bulk of the work)
Unattend.xml  (Instructs WinPE to load the PS script)
shortcutmap.txt (Contains password for mapping folder to store shortcut files)
DatConfig.dat (Contains Dart settings, fixed to use port 3389, you can generate a new one by running the Dart create image tool)
RemoveDartShortcut.ps1 (Removes shortcut script for running machine at the end of your build TS, place this as a step somewhere near the end)
You will need to modify Winpe_Dart.ps1 and include your username and share location. I tested this script initially using a Service Account and storing the password from shortcutmap,txt in a secure string but had all kinds of issues with service accounts and secure strings working together , in the end i had to create a standard user account in AD and use that, you can choose whether or not to then delete the shortcutmap.txt after mapping is complete ( i left it commented out for testing). The script will create shortcuts for dart 7/8/10 however i have commented these out as im only using Dart 10.
Once you are happy that you have your files in order, go ahead and unmount your wim file.
DISM.exe /Unmount-Wim /MountDir:”C:\Users\admin\Desktop\offline” /commit
Bring this Wim file into SCCM and set it as your default PXE boot file,, add your drivers,  also don’t forget to associate it to your task sequences. Oh and dont forget to add powershell component to your boot image.

 

 

 

 

 

 

http://apppackagetips.blogspot.ch/2016/02/dart-remote-control-winpe-nice-way.html

http://deploymentresearch.com/Research/Post/334/Adding-DaRT-8-1-from-MDOP-2013-R2-to-ConfigMgr-2012-R2

http://deploymentresearch.com/Research/Post/250/Software-Assurance-Pays-Off-Remote-Connection-to-WinPE-during-MDT-SCCM-deployments

https://blogs.msdn.microsoft.com/alex_semi/2011/11/29/remote-connection-to-winpe-during-sccm-deployments-creating-shortcuts-with-ticket-numbers-and-ip-on-a-file-share/

Query to show packages with no deployments or task sequences linked


SELECT pkg.Name as [Package Name], pkg.Version, pkg.PackageID,
CASE pkg.PackageType
WHEN 0 THEN 'Software Distribution Package'
WHEN 3 THEN 'Driver Package'
WHEN 4 THEN 'Task Sequence Package'
WHEN 5 THEN 'Software Update Package'
WHEN 6 THEN 'Device Settings Package'
WHEN 7 THEN 'Virtual Package'
WHEN 257 THEN 'Image Package'
WHEN 258 THEN 'Boot Image Package'
WHEN 259 THEN 'OS Install Package'
END AS [Package Type], adv.AdvertisementID, tsp.Name as [TS Name]
FROM v_Package pkg
LEFT JOIN v_Advertisement adv on pkg.PackageID=adv.PackageID
LEFT JOIN v_TaskSequencePackageReferences tsr on pkg.PackageID=tsr.RefPackageID
LEFT JOIN v_TaskSequencePackage tsp on tsr.PackageID=tsp.PackageID
WHERE adv.AdvertisementID is null
AND pkg.PackageType <> 8
AND tsp.Name is null
ORDER BY pkg.PackageType

I added exclusion of PackageType 8 because it is Application model type (which is useless in this query)

source : http://www.jacquesinit.com/blog/sql-query-show-packages-with-no-deployments-or-task-sequences-linked/

Third Party Web interfaces for SCCM (Frontend)

Cireson App portal

Self-Service Portal – Community

 

Configuration Manager Web Frontend Update 2.0

https://scottkeiffer.wordpress.com/2016/09/15/configuration-manager-web-frontend-update-2-0/