-
1. Re: OS_PATCHLEVEL Property is empty for WIN 2012 R2 Servers
Bill RobinsonJun 1, 2016 5:32 PM (in response to Karim Brown)
Is R2 a patch level? it’s not a service pack…
-
2. Re: OS_PATCHLEVEL Property is empty for WIN 2012 R2 Servers
Karim Brown Jun 2, 2016 7:47 AM (in response to Bill Robinson)The Problem is that some BLPckg jobs fails with the error:
Error 02.06.2016 14:04:14 Failed to create file //stphydapp2vp/temp/stage/0a3bd1f2a8113497a34c6228bc1e689e/params.txt. Due to: Evaluating property reference TARGET.OS_PATCHLEVEL resulted in an empty string and is required. Update the Property value before executing the Deploy Job again. the property is managed from BSA itself...
-
3. Re: OS_PATCHLEVEL Property is empty for WIN 2012 R2 Servers
Yanick Girouard Jun 2, 2016 7:52 AM (in response to Karim Brown)What's in that deploy job exactly ? Are you referencing ??TARGET.OS_PATCHLEVEL?? anywhere in the package ?
-
4. Re: OS_PATCHLEVEL Property is empty for WIN 2012 R2 Servers
Karim Brown Jun 15, 2016 6:16 AM (in response to Yanick Girouard)external CommandNr1
SET TDS_RECHNERART="??TARGET.TDS_RECHNERART??"
SET BL_ADMIN_ACCOUNT="??TARGET.ADMIN_ACCOUNT??"
SET BL_ANTIVIRUS="??TARGET.ANTIVIRUS??"
SET BL_AVAILABILITY="??TARGET.AVAILABILITY??"
SET BL_AVAILABILITY_SLA="??TARGET.AVAILABILITY_SLA??"
SET BL_BACKUP_ADMIN="??TARGET.BACKUP_ADMIN??"
SET BL_BUILD_ENVIRONMENT="??TARGET.BUILD_ENVIRONMENT??"
SET BL_BUILTIN_ADMINISTRATOR="??TARGET.BUILTIN_ADMINISTRATOR??"
SET BL_CUSTOMER="??TARGET.CUSTOMER??"
SET BL_DOMAIN="??TARGET.DOMAIN??"
SET BL_ENVIRONMENT="??TARGET.ENVIRONMENT??"
SET BL_FQ_HOST="??TARGET.FQ_HOST??"
SET BL_FUNCTION="??TARGET.FUNCTION??"
SET BL_HOST="??TARGET.HOST??"
SET BL_IP_ADDRESS="??TARGET.IP_ADDRESS??"
SET BL_OS="??TARGET.OS??"
SET BL_OS_PATCHLEVEL="??TARGET.OS_PATCHLEVEL??"
SET BL_OS_PLATFORM="??TARGET.OS_PLATFORM??"
SET BL_OS_RELEASE="??TARGET.OS_RELEASE??"
SET BL_OS_VERSION="??TARGET.OS_VERSION??"
SET PATROL_DIR="??TARGET.PATROL_DIR??"
SET PATROL_INSTALLED_KMS="??TARGET.PATROL_INSTALLED_KMS??"
SET PATROL_USER="??TARGET.PATROL_USER??"
SET BL_SYSTEMDRIVE="??TARGET.SYSTEMDRIVE??"
SET BL_SYSTEMROOT="??TARGET.SYSTEMROOT??"
SET Campany_BL_PROXY_DOMAIN="??TARGET.TDS_BL_PROXY_DOMAIN??"
SET Campany_FACHBEREICH="??TARGET.TDS_FACHBEREICH??"
SET Campany_KUNDE="??TARGET.TDS_KUNDE??"
SET Campany_KUNDENNUMMER="??TARGET.TDS_KUNDENNUMMER??"
SET Campany_MODELL="??TARGET.TDS_MODELL??"
SET Campany_ORT="??TARGET.TDS_ORT??"
SET Campany_PSP_ELEMENT="??TARGET.TDS_PSP_ELEMENT??"
SET Campany_RACK="??TARGET.TDS_RACK??"
SET Campany_RZ="??TARGET.TDS_RZ??"
SET Campany_RZ_KUNDE="??TARGET.TDS_RZ_KUNDE??"
echo Property;Value> C:\tds\conf\prop
echo BL_ADMIN_ACCOUNT;%BL_ADMIN_ACCOUNT%>> C:\tds\conf\prop
echo BL_ANTIVIRUS;%BL_ANTIVIRUS%>> C:\tds\conf\prop
echo BL_AVAILABILITY;%BL_AVAILABILITY%>> C:\tds\conf\prop
echo BL_AVAILABILITY_SLA;%BL_AVAILABILITY_SLA%>> C:\tds\conf\prop
echo BL_BACKUP_ADMIN;%BL_BACKUP_ADMIN%>> C:\tds\conf\prop
echo BL_BUILD_ENVIRONMENT;%BL_BUILD_ENVIRONMENT%>> C:\tds\conf\prop
echo BL_BUILTIN_ADMINISTRATOR;%BL_BUILTIN_ADMINISTRATOR%>> C:\tds\conf\prop
echo BL_CUSTOMER;%BL_CUSTOMER%>> C:\tds\conf\prop
echo BL_DOMAIN;%BL_DOMAIN%>> C:\tds\conf\prop
echo BL_ENVIRONMENT;%BL_ENVIRONMENT%>> C:\tds\conf\prop
echo BL_FQ_HOST;%BL_FQ_HOST%>> C:\tds\conf\prop
echo BL_FUNCTION;%BL_FUNCTION%>> C:\tds\conf\prop
echo BL_HOST;%BL_HOST%>> C:\tds\conf\prop
echo BL_IP_ADDRESS;%BL_IP_ADDRESS%>> C:\tds\conf\prop
echo BL_OS;%BL_OS%>> C:\tds\conf\prop
echo BL_OS_PATCHLEVEL;%BL_OS_PATCHLEVEL%>> C:\tds\conf\prop
echo BL_OS_PLATFORM;%BL_OS_PLATFORM%>> C:\tds\conf\prop
echo BL_OS_RELEASE;%BL_OS_RELEASE%>> C:\tds\conf\prop
echo BL_OS_VERSION;%BL_OS_VERSION%>> C:\tds\conf\prop
echo PATROL_DIR;%PATROL_DIR%>> C:\tds\conf\prop
echo PATROL_INSTALLED_KMS;%PATROL_INSTALLED_KMS%>> C:\tds\conf\prop
echo PATROL_USER;%PATROL_USER%>> C:\tds\conf\prop
echo BL_SYSTEMDRIVE;%BL_SYSTEMDRIVE%>> C:\tds\conf\prop
echo BL_SYSTEMROOT;%BL_SYSTEMROOT%>> C:\tds\conf\prop
echo Campany_RECHNERART;%TDS_RECHNERART%>> C:\tds\conf\prop
echo Campany_BL_PROXY_DOMAIN;%TDS_BL_PROXY_DOMAIN%>> C:\tds\conf\prop
echo Campany_FACHBEREICH;%TDS_FACHBEREICH%>> C:\tds\conf\prop
echo Campany_KUNDE;%TDS_KUNDE%>> C:\tds\conf\prop
echo Campany_KUNDENNUMMER;%TDS_KUNDENNUMMER%>> C:\tds\conf\prop
echo Campany_MODELL;%TDS_MODELL%>> C:\tds\conf\prop
echo Campany_ORT;%TDS_ORT%>> C:\tds\conf\prop
echo Campany_PSP_ELEMENT;%TDS_PSP_ELEMENT%>> C:\tds\conf\prop
echo Campany_RACK;%TDS_RACK%>> C:\tds\conf\prop
echo Campany_RZ;%TDS_RZ%>> C:\tds\conf\prop
echo Campany_RZ_KUNDE;%TDS_RZ_KUNDE%>> C:\tds\conf\prop
-
5. Re: OS_PATCHLEVEL Property is empty for WIN 2012 R2 Servers
Karim Brown Jun 2, 2016 9:27 AM (in response to Yanick Girouard)but the question is why is the property empty? why it sokrs on 2008 for exemple.
I oppned an issue for that:
-
6. Re: OS_PATCHLEVEL Property is empty for WIN 2012 R2 Servers
Yanick Girouard Jun 2, 2016 10:07 AM (in response to Karim Brown)I don't think you can reference an empty property in your BLPackage that way or you'll get this error. The OS_PATCHLEVEL will be empty if it doesn't apply. In the case of Windows 2012 R2, if it doesn't have any service pack applied, it won't have anything in there, it's normal !
-
7. Re: OS_PATCHLEVEL Property is empty for WIN 2012 R2 Servers
Bill RobinsonJun 2, 2016 11:53 AM (in response to Karim Brown)
If you have a 2008 system w/ no service pack applied, non-r2, is it empty ?
-
8. Re: OS_PATCHLEVEL Property is empty for WIN 2012 R2 Servers
Karim Brown Jun 2, 2016 1:49 PM (in response to Bill Robinson)Yes, I checked that and the Property is empty too. But the Job worked bevor.
-
9. Re: OS_PATCHLEVEL Property is empty for WIN 2012 R2 Servers
Karim Brown Jun 2, 2016 1:56 PM (in response to Bill Robinson)Yes, I checked that and the Property is empty too as Janick said. But the Job worked bevor said the BLpakage creator. I will check that in details.
-
10. Re: OS_PATCHLEVEL Property is empty for WIN 2012 R2 Servers
Bill RobinsonJun 2, 2016 1:52 PM (in response to Karim Brown)
worked before meaning what? in 8.5 ? 8.6 ?
-
11. Re: OS_PATCHLEVEL Property is empty for WIN 2012 R2 Servers
Karim Brown Jun 2, 2016 1:59 PM (in response to Bill Robinson)as the BL User said 8.6.1, But let me check that with him in details.
I will update the issue tommorow
-
12. Re: OS_PATCHLEVEL Property is empty for WIN 2012 R2 Servers
Karim Brown Jun 6, 2016 11:37 AM (in response to Karim Brown)sorry, Our BSA User didn't know if it worked bevor in the old versions 8.3. In the BSA Joblogs we have a limit set to 30 days so I cannot check if it worked bevor the upgrade.
Anyway, but I Think the Property schould be set to 0 if there is no Patch installed on targets.
Thanks,
-
13. Re: OS_PATCHLEVEL Property is empty for WIN 2012 R2 Servers
Yanick Girouard Jun 6, 2016 1:39 PM (in response to Karim Brown)Changing the default value of the property has way too much impact on customers. They can't do that. If it's empty, there's no service pack, that's it.
-
14. Re: OS_PATCHLEVEL Property is empty for WIN 2012 R2 Servers
Karim Brown Jun 15, 2016 5:57 AM (in response to Yanick Girouard)I opned an issue for that.
I mean, the other properties works fine even they are empty but not OS_PATCHLEVEL
The Property OS_PATCHLEVEL must be initializated with a value such 0 or something else.
I suggested 0 for empty => that mean No SP is installed
or to give us a possíbility to set the defaultvalue for that property.