אבטחת מידע בכתיבת קוד–רשמים מכנס

December 3, 2017

.האחרון שהתקיים באורלנדו השתתפתי בהרצאה על שילוב אבטחת המידע בתהליך כתיבת הקוד live 360 בכנס . את ההרצאה העביר איש אבטחת המידע של חברת אינטגרציה מובילה בארצות הברית אשר הציג את  המשמעות הכספית והתדמיתית של פגיעה במוצק / חברה כתוצאה מאי הקפדה על אבטחת קוד מתאימה  .(Veracod state of Security 2017 ) למעשה כ 50% מההתקפות שדווחו בשנת 2016 היו בשיכבת האפליקציה , אף שפועל רק כ 1% מכלל תקציבי אבטחת המידע מכוונים לשיכבה זו      :מספר נקודות מרכזיות מההרצאה .  תהליך אבטחת המידע מאופיין כתהליך גוזל משאבים ומכביד   .מבוצע בדרך כלל בתהליך האיפיון הראשוני...
no comments

Microsoft Project Honolulu

November 7, 2017

Honolulu is the new web-based tool for managing Microsoft Windows Server that announced from Microsoft Microsoft invite you to download and start using Project “Honolulu” technical preview today. On Windows Server and Windows Server 2016, Project Honolulu is installed as a network service. You must specify the port that the services listens on, and it requires a certificate for HTTPS. Project Honolulu requires PowerShell features that are not included in Windows Server 2012 and 2012 R2. If you will manage Windows Server 2012 or 2012 R2 with Honolulu, you will need to install WMF version 5.0 or higher on those servers. because...
no comments

Removing Orphaned Virtual Machine Objects in SCVMM (System Center Virtual Machine Manager)

October 25, 2017

  When Managing Virtual Machines via both Hyper-V and SCVMM Sometimes the bond between the Virtual Machine Object on SCVMM and The Hyper-V Breaks This Bond is based on a Property Named VMID that Exists in Both Objects Called VMID When Issue occurs There is a Stale orphaned Virtual Machine object in the SCVMM console and all actions taken on it will fail because the object has no equivalent Virtual Machine in Hyper-V. There is no way to delete this orphaned Virtual Machine Via the Console GUI only thru the powershell command Remove-SCVirtualMachine with the Force Switch(-force). In many cases this happens when a...
tags:
no comments

File Replication Service has detected that the replica set “DOMAIN SYSTEM VOLUME (SYSVOL SHARE)” is in JRNL_WRAP_ERROR

The File Replication Service has detected that the replica set “DOMAIN SYSTEM VOLUME (SYSVOL SHARE)” is in JRNL_WRAP_ERROR. Replica set name is : “DOMAIN SYSTEM VOLUME (SYSVOL SHARE)” Replica root path is : “c:\windows\sysvol\domain” Replica root volume is : \\.\C: A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons. Volume “\\.\C:” has been formatted. The NTFS USN journal on volume “\\.\C:” has been deleted. The NTFS USN journal on volume “\\.\C:” has been truncated. Chkdsk can truncate the journal if...
no comments

Introducing Windows Server 2016, version 1709

October 19, 2017

  Yesterday Microsoft made available Windows Server 2016 version 1709 for download to customers with Software Assurance and for Microsoft Azure  & Amazon customers. This version is the first release in the new Semi-Annual Channel. As Announced a few months ago, Windows Server will be available in two release modules: Long-Term Servicing channel – This Is the current and most familiar module where a new operating system version is released every 2-3 years with 5 years support cycle. Semi-Annual Channel – This new module will offer two new releases every year in spring and fall with new features and roles, support will be...
no comments

What’s happened when you have problem with _msdsc zone

October 17, 2017

  if one or more SRV records are missing from _msdsc zone , you may have problem with Kerberos or Ldap binding . if for Example you have _Kerberos record that missing for one of your Child domain you will have problem with Kerberos authentication (like in Trust or for mange DNS from root parent – “security package specific error occurred” ).   You can recreate the missing zone manually or  The SRV records will be automatically created in the new zone by restarting the NetLogon service on all of your DCs.   SHMUEL H.
no comments

OneDrive new Enterprise features from Ignite 2017

September 28, 2017

מיקרוסופט הכריזה במהלך הכנס על מעבר לגירסת אנטרפרייז שמיועדת לארגונים  עם יכולות הצפנה מתקדמות (תתאפשר הצפנה עם מפתח שהלקוח מביא ולא מפתח שמחולל ע"י מיקרוסופט) ועם יכולות שיחזור (כלקח מהפעילות המוגברת של נוזקות הכופרה ). מיקרוסופט גם מתכננת לשחרר כלי בשרות עצמי שיאפשר למשתמש הגירה קלה ופשוטה מפתרונות אחסון בעננים אחרים או מתקיות משותפות של המשתמש.   OneDrive new Enterprise features    Silent Sync Auto-Account Configuration for OneDrive with ADAL      Option to configure OneDrive when new devices are set up without any user interaction required to do so. Microsoft 365 Powered Device with OneDrive -- Provision PCs over the air without physical interaction with the...
tags:
no comments

Dot net 4.2.6 -Installation failed with error code: (0x800B010A), "A certificate chain could not be built to a trusted root authority."

September 27, 2017

Hi on windows 2008 r2 sp1 when you try to install of Dot net 4.2.6 may fail with the below error message: Installation failed with error code: (0x800B010A), "A certificate chain could not be built to a trusted root authority."   According to the CAPI2 event messages inside the log: <CryptRetrieveObjectByUrlWire> <URL scheme="http">http://www.microsoft.com/pki/certs/MicRooCerAut2011_2011_03_22.crt </URL> <Object type="CONTEXT_OID_CERTIFICATE" constant="1"/> <Timeout>PT15S</Timeout> <Flags value="286005" CRYPT_RETRIEVE_MULTIPLE_OBJECTS="true" CRYPT_WIRE_ONLY_RETRIEVAL="true" CRYPT_LDAP_SCOPE_BASE_ONLY_RETRIEVAL="true" CRYPT_OFFLINE_CHECK_RETRIEVAL="true" CRYPT_AIA_RETRIEVAL="true" CRYPT_PROXY_CACHE_RETRIEVAL="true"/> <AdditionalInfo> <Action name="NetworkRetrievalTimeout"> <Error value="5B4">This operation returned because the timeout period expired. </Error>   Resolution :   use the UI provided by the certmgr.msc MMC snap-in to add certificates to the trusted root store. Right-click the Trusted Root Certification Authorities option to display the All Tasks options. The...
no comments